JDK-8322294 : Cleanup NativePostCallNop
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 21,22,23
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-12-18
  • Updated: 2024-01-16
  • Resolved: 2024-01-10
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 23
23 b05Fixed
Related Reports
Blocks :  
JDK-8290965 - PPC64: Implement post-call NOPs
Description
Cleanup NativePostCallNop

NativePostCallNop and uses of it should be refactored for better separation of shared code from platform details.

- Shared code (e.g. `install_post_call_nop_displacement()`) assumes that a NativePostCallNop can encode 4 bytes of data: 1 byte for the oomap slot and 3 bytes for the offset of the NativePostCallNop in the CodeBlob. It should be left to the platforms how the data is encoded and how many bits are used for oopmap slot / cb offset.

- There is no difference in the implementations of `frame::get_oop_map()`. It should be moved to shared code.
Comments
Changeset: 2e472fe7 Author: Richard Reingruber <rrich@openjdk.org> Date: 2024-01-10 12:18:01 +0000 URL: https://git.openjdk.org/jdk/commit/2e472fe7ea98ca1f07a90d1ad6704e8b2bb3afcf
10-01-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17150 Date: 2023-12-18 22:05:32 +0000
18-12-2023