JDK-6987753 : Specify Methods for Compilation/Inlining at Start
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9,10
- Priority: P5
- Status: Closed
- Resolution: Duplicate
- OS: windows
- CPU: x86
- Submitted: 2010-09-27
- Updated: 2017-01-30
- Resolved: 2017-01-30
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 9 |
|---|
9Resolved  |
Related Reports
|
Duplicate :
|
Description
As of now decision what needs to be compiled and what will be inlined is performed automatically. There are few system wide settings to control this (like inline all methods smaller then this 30 bytes). We know that for majority of client apps some set of methods is always compiled/inlined eventually and often this happens during startup. It seems to have sense to be able to specify set of JRE methods that will be compiled on first occurrence for given app or type of app (like applet). Then compiled version will be used after first iteration and this may improve startup time for the client compiler.
Comments
|