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/code/aotCodeCache.hpp line 222: > 220: > 221: address* _extrs_addr; > 222: address* _stubs_addr; Speaking of UB, `init_extrs` allocates `_stubs_addr` but does not initialize it. It’s probably a wonderful fact that nobody will ever touch the toxic bits of that array, unless they really know somebody else already planted a defined address in it. Still, it feels like jazz dancing at the top of a cliff over a snakepit. Can we please zero out `_stubs_addr` on allocation? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30778#discussion_r4021646166
