Integrated: 8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime

[Doug Simon]

On Wed, 13 Aug 2025 21:18:45 GMT, Doug Simon <dnsimon at openjdk.org> wrote:

> The primary goal of [JDK-8356447](https://bugs.openjdk.org/browse/JDK-8356447) was to have initialization of the Graal JIT occur in the same phase as the rest of VM startup such that initialization problems are detected and reported prior to executing any user code.
> 
> This change caused a performance regression for Truffle when it is used in a JDK that includes both jargraal and libgraal. The problem is that Truffle needs jarjvmci but does not need jargraal when libgraal is available. Initializing jargraal in that configuration delays initialization of Truffle (not just Truffle compilation). Additionally, the jargraal instance created will never be used, wasting memory.
> 
> The solution in this PR is to make EagerJVMCI only apply when initializing JVMCI on a CompileBroker thread.

This pull request has now been integrated.

Changeset: e3aeebec
Author:    Doug Simon <dnsimon at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/e3aeebec1798b9adbb02e11f285951d4275c52e8
Stats:     4 lines in 1 file changed: 3 ins; 0 del; 1 mod

8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime

Reviewed-by: never

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

PR: https://git.openjdk.org/jdk/pull/26768