-
Bug
-
Resolution: Fixed
-
P3
-
7u80, 8u60, 9
-
b64
-
x86
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082705 | emb-9 | Vladimir Kozlov | P3 | Resolved | Fixed | team |
| JDK-8086515 | 8u65 | Vladimir Kozlov | P3 | Resolved | Fixed | b01 |
| JDK-8080314 | 8u60 | Vladimir Kozlov | P3 | Resolved | Fixed | b16 |
| JDK-8137550 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b01 |
| JDK-8081100 | emb-8u60 | Vladimir Kozlov | P3 | Resolved | Fixed | team |
| JDK-8080315 | 7u91 | Andreas Eriksson | P3 | Resolved | Fixed | b01 |
The Vzeroupper instruction introduced in String.equals, String.compareTo and OptimizeFill intrinsic/stubs in the 8011102 changes is the cause.
For 32 byte vectorization, YMM registers are used by the hotspot compiler and the register allocator can allocate these across intrinsic methods.
Vzeroupper in the intrinsic is clobbering upper 16 bytes in all the other YMM registers that are not touched in these methods and so our customers are seeing unexpected results.
- backported by
-
JDK-8080314 8011102 changes may cause incorrect results.
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8279676 Dubious YMM register clearing in x86_64 arraycopy stubs
-
- Resolved
-
-
-
- Resolved
-