RFR: 8359436: AOTCompileEagerly should not be diagnostic

[Aleksey Shipilev]

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

> When AOT code caching is integrated do you plan to move it back to diagnostic? As you said - it does not make sense to touch it.

Right. I think we would need to move it back to diagnostic once AOT code compilation would land. It would also reflect the status of the feature: in JDK 25, it is sensible to flip it back and forth as experimental performance flag; past that, the only sensible behavior is "on", and you only turn it off to diagnose bugs.

What I am trying to achieve with this PR: users in JDK 25 should not be unlocking diagnostic flags for their performance needs. At most, they need to unlock experimental ones.

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

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