-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 8u20, 9
-
Component/s: hotspot
-
b26
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8056668 | emb-9 | Unassigned | P3 | Resolved | Fixed | b26 |
| JDK-8275132 | openjdk8u322 | Unassigned | P3 | Resolved | Fixed | b01 |
| JDK-8274080 | 8u321 | Unassigned | P3 | Resolved | Fixed | b01 |
compiler/intrinsics/bmi/verifycode/ tests on lzcnt and tzcnt based on assumption that REXB prefix used only for Long's intrinsic.
However, tzcnt's and lzcnt's arguments could be placed in R[8-15] registers in Integer's intrinsics too. Also there is no guarantee that arguments will be placed in these registers in Long's intrinsics.
As a results LZcntTestI and TZcntTestI tests fails on Windows-x64, where source argument is placed in R8.
Tests should be updated to remove dependency on REXB occurrence.
However, tzcnt's and lzcnt's arguments could be placed in R[8-15] registers in Integer's intrinsics too. Also there is no guarantee that arguments will be placed in these registers in Long's intrinsics.
As a results LZcntTestI and TZcntTestI tests fails on Windows-x64, where source argument is placed in R8.
Tests should be updated to remove dependency on REXB occurrence.
- backported by
-
JDK-8056668 compiler/intrinsics/bmi/verifycode tests on lzcnt and tzcnt use incorrect assumption about REXB prefix usage
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
-
- Closed
-