Integrated: 8359436: AOTCompileEagerly should not be diagnostic
Aleksey Shipilev
shade at openjdk.org
Tue Jul 1 14:32:51 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`
This pull request has now been integrated.
Changeset: e1382973
Author: Aleksey Shipilev <shade at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/e138297323de3f6990c4c536b1cefd209ce3a69c
Stats: 103 lines in 2 files changed: 102 ins; 0 del; 1 mod
8359436: AOTCompileEagerly should not be diagnostic
Reviewed-by: kvn, syan, dholmes
-------------
PR: https://git.openjdk.org/jdk/pull/25799
More information about the hotspot-runtime-dev
mailing list