RFR: 8345826: Do not automatically resolve jdk.internal.vm.ci when libgraal is used

Doug Simon dnsimon at openjdk.org
Fri May 16 08:36:55 UTC 2025


On Fri, 16 May 2025 08:22:20 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> the set of modules in the training run is the same as the production run

I don't think that's true. That is, I don't think +EnableJVMCI is used in the training run is it @iklam ?

> Is it really terrible to disable the AOTClassLinking optimizations in that scenario?

Depends if you care as much about VM startup when using libgraal as when using C2. Is there a reason why only one of these should have AOTClassLinking startup benefits?

There's also the issue of all the AOTClassLinking tests having to be disabled/ignored/problem listed in the libgraal mach5 tiers. This is what initially motivated @iklam and I to come up with this solution.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/25240#discussion_r2092598097


More information about the graal-dev mailing list