Limit vectorization API to Hotspot VMs (and rename some constants and fix Javadocs) #12765
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I did some tests after fixing the bug in VM option detection.
With OpenJ9 (IBM Semeru) Java v20.0.2 there are no optimizations for Panama Vectors. If you enable the
jdk.incubator.vector
module it is like 1000 times slower, because there's no support at all. The module is there, but fallbacks to the default interpreted mode:Please note: The binary code is not slower, as the vectorization is not used at all:
This PR enables vectorization only if Hotspot was detected by it's JVM flags, any other VM type is logged as not compatible.