JDK-8365256 : RelocIterator should use indexes instead of pointers
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 26
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-08-11
  • Updated: 2025-08-28
  • Resolved: 2025-08-27
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 b13Fixed
Related Reports
Causes :  
JDK-8366269 - SA tests are failing: NullPointerException during stackwalking
Relates :  
JDK-8352112 - [ubsan] hotspot/share/code/relocInfo.cpp:130:37: runtime error: applying non-zero offset 18446744073709551614 to null pointer
Relates :  
JDK-8366341 - [BACKOUT] JDK-8365256: RelocIterator should use indexes instead of pointers
Description
RelocIterator currently uses a pointer to the current element. If we change it to use a base pointer plus an index, then we can undo the workarounds which were introduced in JDK-8352112
Comments
Changeset: 88c39793 Branch: master Author: Johan Sjölen <jsjolen@openjdk.org> Date: 2025-08-27 07:55:57 +0000 URL: https://git.openjdk.org/jdk/commit/88c39793670f2d36490530993feb60e138f43a70
27-08-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/26569 Date: 2025-07-31 06:17:24 +0000
11-08-2025