JDK-8306659 : Deoptimization does not preserve larval state for rematerialized objects.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2023-04-21
  • Updated: 2023-04-21
  • Resolved: 2023-04-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-valhallaResolved
Related Reports
Duplicate :  
JDK-8239003 - [lworld] C2 should respect larval state when scalarizing
Description
- Unsafe.makePrivateBuffer() can allocate a value object in mutable state by setting a larval state flag in its markword.

- Currently C2 compiler's SafePointScalarObjectNode does not propagate larval state information, thus during de-optimization a newly rematerialized instance does not carry valid larval state and this can cause problems during subsequent Unsafe.put operations by interpreter.
Comments
This is a duplicate of JDK-8239003. Feel free to take that one, [~jbhateja]. Christian is not (yet) working on it.
21-04-2023