-
Bug
-
Resolution: Fixed
-
P2
-
11.0.6, 11.0.6-oracle, 14
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8241572 | 13.0.3 | Sandhya Viswanathan | P2 | Resolved | Fixed | b02 |
| JDK-8235393 | 11.0.7-oracle | Sandhya Viswanathan | P2 | Closed | Fixed | b01 |
| JDK-8238541 | 11.0.7 | Sandhya Viswanathan | P2 | Resolved | Fixed | b03 |
On Skylake platform the JVM by default sets the UseAVX level to 2 and accordingly sets MaxVectorSize to 32 bytes as per JDK-8221092.
When the user explicitly want to use AVX3 on skylake platform they need to invoke the JVM with -XX:UseAVX=3 command line argument. This should aumatically result in MaxVectorSize being set to 64 bytes. However postJDK-8221092, when -XX:UseAVX=3 is given on command line, the MaxVectorSize is being wrongly set to 16 bytes.
When the user explicitly want to use AVX3 on skylake platform they need to invoke the JVM with -XX:UseAVX=3 command line argument. This should aumatically result in MaxVectorSize being set to 64 bytes. However post
- backported by
-
JDK-8238541 MaxVectorSize set wrongly when UseAVX=3 is specified after JDK-8221092
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-