Only under special AOT flag or in debug VM failure to generate or load AOT code should cause VM exit with message or hit assert/fatal.
By default the failed AOT code should be discarded with UL message about it by request (log_info) and VM and AOT process should continue run. Or stop AOT code processing (for exampale, when no reserved memory for AOT code left).
Unless we hit some catastrophic failure: OOM fro example. This is similar how JIT compilers behave.
By default the failed AOT code should be discarded with UL message about it by request (log_info) and VM and AOT process should continue run. Or stop AOT code processing (for exampale, when no reserved memory for AOT code left).
Unless we hit some catastrophic failure: OOM fro example. This is similar how JIT compilers behave.
- relates to
-
JDK-8358690 Some initialization code asks for AOT cache status way too early
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/e3eb089d
-
Review(master)
openjdk/jdk/25525