JDK-6919069 : client compiler needs to capture more profile information for tiered work
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-01-22
- Updated: 2011-04-23
- Resolved: 2011-04-23
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 |
|---|---|---|
6u25Fixed  |
7Fixed |
hs20Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The client compiler (C1), when used as tier 1, has the job of collecting profile information instead of the interpreter. Currently, it does not collect full information for checkcast, instanceof, or aastore instructions. This should be fixed, to avoid needless performance regressions in tiered systems. Bugs 6912064 and 6919064 when fixed will cause the server compiler to use more profile information; work on C1 should track these profile inputs (in the interpreter) and outputs (in the server compiler) and keep parity with the interpreter.
Comments
|