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: 2025-10-16
  • 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.
JDK 9
9 b108Fixed
Related Reports
Relates :  
JDK-8161245 - Enums should be fully optimized
Relates :  
JDK-8369993 - Redundant separate 'String' check in 'trust_final_non_static_fields' ciField.cpp
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.
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/9cf33e51c2d4 User: lana Date: 2016-03-02 19:34:38 +0000
02-03-2016
URL: http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/rev/9cf33e51c2d4 User: shade Date: 2016-02-16 09:04:28 +0000
16-02-2016