RFR: 8359436: AOTCompileEagerly should not be diagnostic

Vladimir Kozlov kvn at openjdk.org
Fri Jun 13 17:18:30 UTC 2025


On Fri, 13 Jun 2025 11:31:27 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

> A new AOTCompileEagerly flag introduced by [JDK-8355003](https://bugs.openjdk.org/browse/JDK-8355003) is marked as diagnostic. However, this flag guards the experimental feature, that is, whether the existence of AOT profiles should trigger immediate JIT compilation. Therefore, this flag should be at least be "experimental", rather than "diagnostic".
> 
> I don't think it makes sense to elevate this flag to full product flag, since 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.
> 
> Additional testing:
>  - [x] Linux x86_64 server fastdebug, `runtime/cds`

Okay. Then why not do this change in JDK 25 branch only and don't touch JDK 26?
You would need approval for JDK 25: https://openjdk.org/jeps/3#Late-Enhancement-Request-Process

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

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


More information about the hotspot-runtime-dev mailing list