-
Bug
-
Resolution: Duplicate
-
P4
-
repo-valhalla
-
generic
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.
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.
- duplicates
-
JDK-8322547 [lworld] Add support for larval bit preservation during de-optimization.
- Open