On Mon, 2 Nov 2026 14:30:49 GMT, Chen Liang <[email protected]> wrote:
>> Represent Vector API payload objects (`Vector`, `VectorMask`, >> `VectorShuffle`) and `Float16` as value objects when preview features are >> enabled. This makes them more closely resemble the SIMD registers they try >> to model. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Chen Liang has updated the pull request with a new target base due to a merge > or a rebase. The pull request now contains seven commits: > > - Merge branch 'master' of github.com:openjdk/jdk into exp/vector-value-decl > - Merge branch 'master' of github.com:openjdk/jdk into exp/vector-value-decl > - Vector value JVM support > - Merge branch 'master' of github.com:openjdk/jdk into exp/vector-value-decl > - Merge branch 'master' of github.com:openjdk/jdk into exp/vector-value-decl > - Merge branch 'master' of github.com:openjdk/jdk into exp/vector-value-decl > - Vector API can be value classes! This is okay, being value objects mean it is allowed for random `Vector` objects to suddenly pass `==` checks. The Multifield things won't be ported, it does not provide performance for SIMD register operations because it falls back to memory, cannot guarantee alignment, and imposts huge implement costs to the JVM. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32113#issuecomment-6585108377
