JDK-8359436 : AOTCompileEagerly should not be diagnostic
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 25,26
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-06-13
  • Updated: 2025-07-03
  • Resolved: 2025-07-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25 JDK 26
25Fixed 26 b05Fixed
Related Reports
Relates :  
Description
A new AOTCompileEagerly flag introduced by 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.
Comments
A pull request was submitted for review. Branch: jdk25 URL: https://git.openjdk.org/jdk/pull/26073 Date: 2025-07-01 15:33:56 +0000
01-07-2025

Changeset: e1382973 Branch: master Author: Aleksey Shipilev <shade@openjdk.org> Date: 2025-07-01 14:30:20 +0000 URL: https://git.openjdk.org/jdk/commit/e138297323de3f6990c4c536b1cefd209ce3a69c
01-07-2025

Late enhancement request approved by Project Lead.
01-07-2025

Late Enhancement Request (25) Changes the flag from diagnostic to experimental, to underline the intended behavior/expectation in JDK 25. Risk is low, changes the flag from one non-fully-supported flags class not another. I plan to integrate the change to JDK 25 in a week following mainline integration.
25-06-2025

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/25799 Date: 2025-06-13 11:31:27 +0000
13-06-2025