RFR: 8365468: EagerJVMCI should only apply to the CompilerBroker JVMCI runtime [v2]

[Doug Simon]

On Wed, 13 Aug 2025 21:48:51 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.
>
> Doug Simon has refreshed the contents of this pull request, and previous commits have been removed. The incremental views will show differences compared to the previous content of the PR. The pull request contains one new commit since the last revision:
> 
>   only apply EagerJVMCI on a CompileBroker thread

Thanks for the review.

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

PR Comment: https://git.openjdk.org/jdk/pull/26768#issuecomment-3190847699