JDK-8370133 : C2: Manage non-debug safepoint edges in structural manner
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 26
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-10-17
  • Updated: 2025-10-17
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
tbdUnresolved
Related Reports
Relates :  
JDK-8290892 - C2: Intrinsify Reference.reachabilityFence
Description
There are multiple places where non-debug inputs are added to safepoints, but there's no functionality to separate different types of edges, so it's easy to break things when different flavors mix. (In particular, reachability edges introduced by JDK-8290892, derived oops, exception oops during parsing, valid_length_test_input on array allocation runtime calls).

Track non-debug inputs of different types separately and let corresponding code query the type of non-debug inputs it is interested in.