RFR: 8257220: [JVMCI] option validation should not result in a heavy-weight VM crash

Tobias Hartmann thartmann at openjdk.java.net
Tue Dec 1 07:41:56 UTC 2020


On Mon, 30 Nov 2020 22:51:19 GMT, Doug Simon <dnsimon at openjdk.org> wrote:

>> @dougxc  I still got crash with -Xcomp:
>> java -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+UseJVMCICompiler -Xcomp -version
>> Exception during JVMCI compiler initialization
>> jdk.vm.ci.common.JVMCIError: no JVMCI compiler selected: default compiler is not found
>> 	at jdk.vm.ci.hotspot.HotSpotJVMCICompilerConfig$DummyCompilerFactory.compileMethod(jdk.internal.vm.ci at 16-internal/HotSpotJVMCICompilerConfig.java:58)
>> 	at jdk.vm.ci.hotspot.HotSpotJVMCICompilerConfig$DummyCompilerFactory.compileMethod(jdk.internal.vm.ci at 16-internal/HotSpotJVMCICompilerConfig.java:48)
>> 	at jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.compileMethod(jdk.internal.vm.ci at 16-internal/HotSpotJVMCIRuntime.java:807)
>> # To suppress the following error report, specify this argument
>> # after -XX: or in .hotspotrc:  SuppressErrorAt=/jvmciRuntime.cpp:1102
>> #
>> # A fatal error has been detected by the Java Runtime Environment:
>> #
>> #  Internal Error (/jdk_git/open/src/hotspot/share/jvmci/jvmciRuntime.cpp:1102), pid=3015811, tid=3015824
>> #  fatal error: Fatal exception in JVMCI: Exception during JVMCI compiler initialization
>> #
>> # JRE version: Java(TM) SE Runtime Environment (16.0) (fastdebug build 16-internal+0-2020-11-30-2007459.vkozlov...)
>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 16-internal+0-2020-11-30-2007459.vkozlov..., compiled mode, sharing, tiered, jvmci, jvmci compiler, compressed oops, g1 gc, linux-amd64)
>> # Problematic frame:
>> # V  [libjvm.so+0x116b950]  JVMCIRuntime::fatal_exception(JVMCIEnv*, char const*)+0x90
>> #
>> # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /jdk_git/core.3015811)
>> #
>> # An error report file with more information is saved as:
>> # /jdk_git/hs_err_pid3015811.log
>
> This PR was about improving the failure mode when incorrect `-Djvmci` properties are specified.
> The case you are highlighting is when misconfiguration happens with JVMCI related VM flags. In this case, I guess JVMCI initialization could detect the conflict between `-XX:+UseJVMCICompiler` and the lack of a JVMCI compiler in the VM (now the default).

Looks related to [JDK-8257471](https://bugs.openjdk.java.net/browse/JDK-8257471).

-------------

PR: https://git.openjdk.java.net/jdk/pull/1487


More information about the hotspot-compiler-dev mailing list