Skip to content

8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime #26768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime #26768

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotJVMCIRuntime.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,10 @@ public static HotSpotJVMCIRuntime runtime() {
// Can only do eager initialization of the JVMCI compiler
// once the singleton instance is available.
if (result.config.getFlag("EagerJVMCI", Boolean.class)) {
result.getCompiler();
// EagerJVMCI only applies to JVMCI when used by the CompileBroker.
if (result.getCompilerToVM().isCompilerThread()) {
result.getCompiler();
}
}
}
// Ensures JVMCIRuntime::_HotSpotJVMCIRuntime_instance is
Expand Down