JDK-8326598 : [lworld] JVM must support field inheritance for value classes
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: repo-valhalla
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-02-23
  • Updated: 2024-07-01
  • Resolved: 2024-05-21
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-valhallaFixed
Related Reports
Duplicate :  
JDK-8331504 - [lworld] Add field inheritance to value classes
Duplicate :  
JDK-8328419 - [lworld] Reimplement TestSuperClasses for JEP401
Duplicate :  
JDK-8328417 - [lworld] Reimplement TestClassModifiers for JEP401
Relates :  
JDK-8331964 - [lworld] Field inheritance in value classes causes C2 crashes
Description
In LW5 and previous model, value classes were not allowed to inherit fields from a super class.

JEP 401 allows a value class to inherit non-static fields from a super value abstract class. Class file validation and field layout computation must be adjusted to this new rule.

Warning: this rule enables a new kind of circularity, where a value abstract class declares a non-static field with type one of the class sub-value class.
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/valhalla/pull/1103 Date: 2024-05-08 19:42:31 +0000
09-05-2024