JDK-6523546 : compiler interface should be initialized lazily
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2007-02-09
- Updated: 2013-11-01
- Resolved: 2007-03-15
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.
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 6 | JDK 7 | Other |
|---|---|---|
6u4Fixed  |
7Fixed |
hs10Fixed |
Description
The compiler interface is initialized by the thread that is creating the jvm. This should be defered until we actually need the compilers. This will help startup on machines with more than one cpu since we can execute bytecodes sooner and we can initialize the ci in a compiler thread.
Comments
|