-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b16
-
generic
-
generic
See the discussion in https://github.com/openjdk/jdk/pull/8877#issuecomment-1144247578. The option SuperWordMaxVectorSize was introduced in JDK19 as a temporary solution to fix a performance issue on x86 cascade lake machines. The implementation is fine for current aarch64 hardware, but SVE architectures supports more than 512 bits.
Also, the patch handled SuperWordMaxVectorSize on vm version level only for x86 platform and missed other platforms, see the discussion in https://github.com/openjdk/jdk/pull/12350#discussion_r1126106213.
The task is to drop the global option but keep the performance fix on the x86 backend, to reduce side effect for other platforms.
Also, the patch handled SuperWordMaxVectorSize on vm version level only for x86 platform and missed other platforms, see the discussion in https://github.com/openjdk/jdk/pull/12350#discussion_r1126106213.
The task is to drop the global option but keep the performance fix on the x86 backend, to reduce side effect for other platforms.
- relates to
-
JDK-8287697 Limit auto vectorization to 32-byte vector on Cascade Lake
-
- Resolved
-