The vector API is designed to specific vector communications that reliably compile at runtime to optimum vector directions on supported CPU architectures, thus attaining efficiency superior to equal scalar computations. The vector API beforehand was incubated in JDK 16 by means of JDK 23. Goals of the proposal embody clearly and concisely expressing a variety of vector computations in an API that’s platform-agnostic, that gives dependable runtime compilation and efficiency on x64 and AArch54 architectures, that degrades gracefully and nonetheless features when a vector computation can’t be expressed at runtime, and that aligns with Project Valhalla, leveraging enhancements to the Java object mannequin.
The class-file API, beforehand previewed in JDK 22 and JDK 23, can be finalized in JDK 24, with minor adjustments. This API supplies a typical API for parsing, producing, and reworking Java class information. It goals to offer an API for processing class information that tracks the category file format outlined by the Java Virtual Machine specification. A second objective is to allow JDK elements emigrate to the usual API, and finally take away the JDK’s inside copy of the third-party ASM library. Changes because the second preview embody a renaming of enum values, elimination of some fields, the addition of strategies and methodology overloads, strategies renamed, and elimination of interfaces and strategies deemed pointless.
Late barrier enlargement for the G1 rubbish collector is meant to simplify the implementation of G1’s boundaries by shifting their enlargement from early within the C2 compilation pipeline to later. The boundaries file details about software reminiscence accesses. Goals embody decreasing the execution time of C2 compilation when utilizing the G1 collector, making G1 boundaries understandable to HotSpot builders who lack a deep understanding of C2, and guaranteeing that C2 preserves invariants concerning the relative ordering of reminiscence accesses, safepoints, and boundaries. A fourth function is preserving the standard of C2-generated JIT (just-in-time)-compiled code, by way of velocity and dimension.