JDK-8298089 : Rename Opaque nodes to something more useful
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 20
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2022-12-05
  • Updated: 2022-12-05
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8294540 - Remove Opaque2Node: it is broken and triggers assert
Relates :  
JDK-8288981 - C2: Fix issues with skeleton predicates
Description
We used to have
Opaque1, Opaque2, Opaque3, Opaque4.
In JDK-8294540 we remove Opaque2, so the numbering is broken.
The numbering is meaningless anyway.
Rename the nodes so that they relate to their function more directly, and one does not always have to guess / research what they are for.
Opaque4 might go away / be renamed after JDK-8288981, but it would be fine to rename them already now.