JDK-8371804 : C2: Tighten up LoadNode::Value comments after JDK-8346184
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-11-13
  • Updated: 2025-11-24
  • Resolved: 2025-11-14
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.
JDK 26
26 b25Fixed
Related Reports
Causes :  
JDK-8346184 - C2: assert(has_node(i)) failed during split thru phi
Description
This confused me quite a bit in JDK-8371581 investigations. 

With JDK-8346184, I see we have moved the block in LoadNode::Value that produced bottom values for the block that "If we are loading from a freshly-allocated object, produce a zero, if the load is provably beyond the header of the object." This comment is misleading, and really related to the old place, which actually returns zeroes.

It would be better to clean this up to avoid further confusion. There should be no semantic change, only the cleanup.
Comments
Changeset: 10f262a6 Branch: master Author: Aleksey Shipilev <shade@openjdk.org> Date: 2025-11-14 15:31:28 +0000 URL: https://git.openjdk.org/jdk/commit/10f262a6ad9a6e89cd79409c5e1a3f7efda76928
14-11-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/28296 Date: 2025-11-13 14:30:10 +0000
13-11-2025