The vector API is designed to precise vector communications that reliably compile at runtime to optimum vector directions on supported CPU architectures, thus reaching efficiency superior to equal scalar computations. The vector API beforehand was incubated in JDK 16 by means of JDK 23. Objectives of the proposal embrace 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 Mission Valhalla, leveraging enhancements to the Java object mannequin.
The class-file API, beforehand previewed in JDK 22 and JDK 23, could be finalized in JDK 24, with minor adjustments. This API offers a regular API for parsing, producing, and remodeling Java class recordsdata. It goals to supply an API for processing class recordsdata that tracks the category file format outlined by the Java Digital Machine specification. A second purpose is to allow JDK elements emigrate to the usual API, and finally take away the JDK’s inner copy of the third-party ASM library. Adjustments for the reason that second preview embrace a renaming of enum values, elimination of some fields, the addition of strategies and technique 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 limitations by shifting their enlargement from early within the C2 compilation pipeline to later. The limitations document details about utility reminiscence accesses. Objectives embrace lowering the execution time of C2 compilation when utilizing the G1 collector, making G1 limitations understandable to HotSpot builders who lack a deep understanding of C2, and guaranteeing that C2 preserves invariants in regards to the relative ordering of reminiscence accesses, safepoints, and limitations. A fourth characteristic is preserving the standard of C2-generated JIT (just-in-time)-compiled code, by way of velocity and dimension.
