JDK-8034855 : Toolkit class should not disable JIT compiler
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2014-02-13
  • Updated: 2014-02-17
  • Resolved: 2014-02-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-6744401 - Consider removal of code disabling JIT in Toolkit.getDefaultToolkit
Description
Historically toolkit a class switches off JIT compilation. It is necessary to check why we do it, and how performance is affected.
See java.awt.Toolki.java
    public static synchronized Toolkit getDefaultToolkit() {
........................
                // We disable the JIT during toolkit initialization.  This
                // tends to touch lots of classes that aren't needed again
                // later and therefore JITing is counter-productiive.
                java.lang.Compiler.disable();
.......................
                // Make sure to always re-enable the JIT.
                java.lang.Compiler.enable();