JDK-8298099 : [JVMCI] decouple libgraal from JVMCI module at runtime
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-12-05
  • Updated: 2022-12-12
  • Resolved: 2022-12-07
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 b27Fixed
Description
Libgraal is compiled ahead of time and should not need any JVMCI Java code to be dynamically loaded at runtime. Currently this is not the case due to the following:

* Code to copy system properties from the HotSpot heap into the libgraal heap. This is in jdk.vm.ci.services.Services.initializeSavedProperties(byte[]) and jdk.vm.ci.services.Services.serializeSavedProperties(). This code should be moved to java.base/jdk.internal.vm.VMSupport.
* Code to translate exceptions from the HotSpot heap into the libgraal heap and vice versa. This code should be moved from jdk.internal.vm.ci//jdk.vm.ci.hotspot.TranslatedException to java.base/jdk.internal.vm.VMSupport.

Resolving this issue will allow for building a JDK image that includes (and uses) libgraal but does not include jdk.internal.vm.ci or jdk.internal.vm.compiler.
Comments
Changeset: 8b69a2e4 Author: Doug Simon <dnsimon@openjdk.org> Date: 2022-12-07 22:11:11 +0000 URL: https://git.openjdk.org/jdk/commit/8b69a2e434ad2fa3369079622b57afb973d5bd9a
07-12-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/11513 Date: 2022-12-05 13:16:25 +0000
05-12-2022