-
Bug
-
Resolution: Unresolved
-
P4
-
repo-metropolis
libgraal should not have a reference to classes in JVMCI and Graal modules.
Otherwise it will have the same issues:
- Effects on Java heap, metaspace
- Effects on GC and JVMTI events
- Pollution of code profiling
- (CNF) as Java Graal with Java options which limit modules:
$ java --limit-modules java.base -Xbatch -version
Uncaught exception exiting JVMCIEnv scope entered at open/src/hotspot/share/jvmci/jvmciRuntime.cpp:641
Exception in thread "main": jdk.vm.ci.common.JVMCIError
jdk.vm.ci.common.JVMCIError: java.lang.ClassNotFoundException: jdk.internal.vm.compiler.word.WordBase
at jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.createClass(HotSpotJVMCIRuntime.java:503)
Otherwise it will have the same issues:
- Effects on Java heap, metaspace
- Effects on GC and JVMTI events
- Pollution of code profiling
- (CNF) as Java Graal with Java options which limit modules:
$ java --limit-modules java.base -Xbatch -version
Uncaught exception exiting JVMCIEnv scope entered at open/src/hotspot/share/jvmci/jvmciRuntime.cpp:641
Exception in thread "main": jdk.vm.ci.common.JVMCIError
jdk.vm.ci.common.JVMCIError: java.lang.ClassNotFoundException: jdk.internal.vm.compiler.word.WordBase
at jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.createClass(HotSpotJVMCIRuntime.java:503)