JDK-8296950 : [lworld] AccessFlags should be specific to class file version
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang:reflect
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2022-11-14
  • Updated: 2022-11-18
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
repo-valhallaUnresolved
Related Reports
Cloners :  
JDK-8297271 - AccessFlags should be specific to class file version
Relates :  
JDK-8291360 - Create entry points to expose low-level class file information
Relates :  
JDK-8266670 - Better modeling of access flags in core reflection
Description
Some access flags apply only to class files with a range of class file versions.
The java.lang.AccessFlag class should return the AccessFlag corresponding to the actual accessflags that appear in the class file and depending on the class file version.
For example, Valhalla proposes to change the meaning of 0x0020 from ACC_SUPER to ACC_IDENTITY.  j.l.Class.accessFlags() should return the appropriate flags depending on the class file version.
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/valhalla/pull/808 Date: 2022-11-14 21:12:30 +0000
14-11-2022