RFR: 8359436: AOTCompileEagerly should not be diagnostic [v3]

[Aleksey Shipilev]

On Wed, 25 Jun 2025 10:13:49 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`
>
> Aleksey Shipilev has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains five additional commits since the last revision:
> 
>  - Add bug line
>  - Merge branch 'master' into JDK-8359436-aot-diagnostic
>  - Merge branch 'master' into JDK-8359436-aot-diagnostic
>  - Test
>  - Fix

JDK 25 enhancement request granted. I am integrating this to mainline, and would follow with JDK 25 backport.

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

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