JDK-8289925 : Shared code shouldn't reference the platform specific method frame::interpreter_frame_last_sp()
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-07-07
  • Updated: 2022-10-10
  • Resolved: 2022-10-05
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 20
20 b18Fixed
Related Reports
Blocks :  
JDK-8286302 - Port JEP 425 to PPC64
Blocks :  
JDK-8294284 - Loom: make use of frame::is_older() and frame::id() to reduce dependency on growth direction of stacks
Description
The method `frame::interpreter_frame_last_sp()` is a platform method in the sense that it is not declared in a shared header file. It is declared and defined on some platforms though (x86 and aarch64 I think).

`frame::interpreter_frame_last_sp()` existed on these platforms before vm continuations (aka loom). Shared code that is part of the vm continuations implementation references it. This breaks the platform abstraction.
Comments
Changeset: ee6c3917 Author: Richard Reingruber <rrich@openjdk.org> Date: 2022-10-05 14:10:02 +0000 URL: https://git.openjdk.org/jdk/commit/ee6c39175bc47608282c52c575ce908399349e7c
05-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/9411 Date: 2022-07-07 16:02:19 +0000
08-07-2022
Accidentely marked as resolved.
07-07-2022