JDK-8339113 : AccessFlags can be u2 in metadata
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2024-08-27
  • Updated: 2025-01-07
  • Resolved: 2025-01-07
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 25
25 masterFixed
Related Reports
Cloners :  
JDK-8347147 - [REDO] AccessFlags can be u2 in metadata
Relates :  
JDK-8345678 - compute_modifiers should not be in create_mirror
Relates :  
JDK-8293118 - AccessFlags should be just the classfile flags
Description
After the Klass flags are moved, AccessFlags can be accessed as an unsigned short.  A lot of assembly code in the interpreter and compiler generated code needs to be adjusted for this.
But it would save space in Metadata for this field (realigning other fields to avoid alignment gaps).
Comments
Backed out as we need to coordinate with a Graal change.
07-01-2025
Changeset: 098afc8b Branch: master Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2025-01-07 22:03:38 +0000 URL: https://git.openjdk.org/jdk/commit/098afc8b7d0e7caa82999fb9d4e319ea8aed09a1
07-01-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/22246 Date: 2024-11-19 16:18:48 +0000
17-12-2024