On Tue, 15 Sep 2026 22:08:12 GMT, Vladimir Kozlov <[email protected]> wrote:
>> Improve startup and warmup time by making optimized native code for an >> application instantly available when the HotSpot Java Virtual Machine >> starts. Achieve this by compiling application code to native code in a >> training run, storing the native code in the [AOT >> cache](https://openjdk.org/jeps/483#Description) for use in subsequent >> production runs. >> >> More details in the [JEP](https://openjdk.org/jeps/544). >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Vladimir Kozlov has updated the pull request incrementally with one > additional commit since the last revision: > > More cleanups and fixes. Includes RISC-V suggested changes. src/hotspot/share/compiler/compileBroker.cpp line 863: > 861: if (is_aot_thread) { > 862: int num = comp->num_aot_compiler_threads() + 1; > 863: comp->set_num_aot_compiler_threads(num); How is this update serialized relative to other threads which might be creating threads? Or is this only done in a single-threaded context? It’s not clear from reading the code locally – par for HotSpot, I guess. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30778#discussion_r4021361142
