JDK-8322540 : [lworld] Missing value object state population during scalarization.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • CPU: generic
  • Submitted: 2023-12-20
  • Updated: 2024-01-03
  • Resolved: 2024-01-03
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 :  
Description
Assignment to non-flat field should always be buffered. Since buffering and scalarization are orthogonal concepts. Thus, non-flattened field can still be scalarized and directly passed to it users. 

In that case buffer allocation becomes redundant and should be eliminated, in other words if initializing field values are forwarded to its users then allocation becomes redundant.

Compiler still need to create a SafePointScalarObjectNode for eliminated allocation, this is needed for ObjectValue construction and subsequent use for object reconstruction during de-optimization.

Currently we miss appending larval and init state information of a value object to SafePoint nodes.


Comments
Will be addressed by JDK-8322547.
21-12-2023