Skip to content- Sources: primary, discussion
- Summary: XPipe reports that since JDK 25 an AOT cache with class linking also stores adapter code generated for the training machine's CPU, causing SIGILL crashes on hosts without features such as AVX-512, tracked as JDK-8388703. The workaround is -XX:+UnlockDiagnosticVMOptions -XX:-AOTAdapterCaching at cache creation, and JDK 27 will only use cached adapters on an exact CPU feature match. The post also lists JVM options and incubating modules that silently disable AOT class linking.
- Why it matters: Teams building AOT caches in CI for heterogeneous fleets need the adapter caching flag and should verify class linking in -Xlog:aot output.