Description
The notion of flattenable field has evolved over time with the different models the Valhalla project has implemented. From the access flag JVM_ACC_FLATTENABLE generated by javac, then the JVM_ACC_FIELD_FLATTENABLE VM internal flag computed from the L/Q model, and now in LW3, the notion of flattenable field is quite obsolete (a field with an inline type is always flattenable, no side bit/information, the type of the field says everything).
The current code in the JVM still has remains of the different models and their different implementations, leading to duplications of code or bits to encode the flattenable nature of a field.
It's time to cleanup the code and remove the traces of the old models.
The current code in the JVM still has remains of the different models and their different implementations, leading to duplications of code or bits to encode the flattenable nature of a field.
It's time to cleanup the code and remove the traces of the old models.
Attachments
Issue Links
- relates to
-
JDK-8247590 [lworld] JVM_ACC_FIELD_INLINED clashes with ENUM
- Resolved
-
JDK-8249869 [lworld] Remove LW2 specific code from the JIT
- Resolved
-
JDK-8247578 [lworld] New inlined JVM internal field access constant in java.base
- Resolved