JDK-8149813 : Move trusted final field handling from C2 LoadNode::Value to shared code
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-02-15
- Updated: 2016-07-13
- Resolved: 2016-02-16
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 |
|---|
9 b108Fixed  |
Related Reports
|
Relates :
|
Description
Currently, C2 has its own constant folding for final fields in primitive boxes and String in LoadNode::Value. But for quite some time now, we have a shared infra in CI that communicates what final fields in JDK can be trusted by compilers. As the cleanup, we'd want to remove the C2-specific handling, and instead spell out these special cases in shared code. The side benefit would be C1 picking up optimizations too.