RFR: 8144944: JVMCI compiler initialization can happen on different thread than JVMCI initialization

Doug Simon doug.simon at oracle.com
Tue Dec 8 22:07:02 UTC 2015


The timer used for JVMCI related initialization (enabled by -Djvmci.inittimer=true) currently assumes that all JVMCI related initialization happens on the same thread. This is wrong. While all related initialization should happen on the same thread, core JVMCI initialization may be performed by one compiler thread and JVMCI compiler (e.g., Graal) initialization may be performed on a different compiler thread.

For example, one compiler thread may be the first to execute:

http://hg.openjdk.java.net/graal/graal-jvmci-9/hotspot/file/7a570929c5e5/src/share/vm/jvmci/jvmciCompiler.cpp#l129

which can trigger core JVMCI initialization while a different compiler thread is the first to reach:

http://hg.openjdk.java.net/graal/graal-jvmci-9/hotspot/file/7a570929c5e5/src/share/vm/jvmci/jvmciCompiler.cpp#l145

which triggers JVMCI compiler initialization.

https://bugs.openjdk.java.net/browse/JDK-8144944
http://cr.openjdk.java.net/~dnsimon/8144944/

-Doug


More information about the hotspot-compiler-dev mailing list