RFR: 8359436: AOTCompileEagerly should not be diagnostic

Aleksey Shipilev shade at openjdk.org
Fri Jun 13 15:52:35 UTC 2025


On Fri, 13 Jun 2025 13:27:43 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:

> > once AOT code caching arrives, this flag would default to true, and would cause AOT loads instead of JIT compilations. Disabling the flag by user choice would be significantly counter-productive then.
> 
> Why do you need to change it then?

Because in JDK 25, I can see people experimenting with this option, or even turning it on. It is inconvenient to turn on diagnostic option for production use.

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

PR Comment: https://git.openjdk.org/jdk/pull/25799#issuecomment-2970804695


More information about the hotspot-runtime-dev mailing list