Skip to content

Commit e68f650

Browse files
Doug Simondougxc
authored andcommitted
8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime
Reviewed-by: never (cherry picked from commit e3aeebe)
1 parent f5699db commit e68f650

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotJVMCIRuntime.java

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,10 @@ public static HotSpotJVMCIRuntime runtime() {
186186
// Can only do eager initialization of the JVMCI compiler
187187
// once the singleton instance is available.
188188
if (result.config.getFlag("EagerJVMCI", Boolean.class)) {
189-
result.getCompiler();
189+
// EagerJVMCI only applies to JVMCI when used by the CompileBroker.
190+
if (result.getCompilerToVM().isCompilerThread()) {
191+
result.getCompiler();
192+
}
190193
}
191194
}
192195
// Ensures JVMCIRuntime::_HotSpotJVMCIRuntime_instance is

0 commit comments

Comments
 (0)