-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 21, 22
-
b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8323382 | 21.0.3-oracle | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
| JDK-8320076 | 21.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b08 |
While doing JDK-8316961, I noticed that atomic tests behave weirdly when executed from gtest. I believe the reason is that tests are running as TEST, not as TEST_VM. So the VM is not initialized, which fails the tests on asserts and/or takes weird paths in the atomic code.
Some Atomic implementations reach to VM_Version for asserts:
https://github.com/openjdk/jdk/blob/9cf334fb6488188ea4236e5d156b11245bace88f/src/hotspot/os_cpu/linux_arm/atomic_linux_arm.hpp#L149
Some Atomic implementations reach to StubRoutines for fallbacks:
https://github.com/openjdk/jdk/blob/9cf334fb6488188ea4236e5d156b11245bace88f/src/hotspot/os_cpu/linux_arm/os_linux_arm.cpp#L520
Some Atomic implementations reach to VM_Version for asserts:
https://github.com/openjdk/jdk/blob/9cf334fb6488188ea4236e5d156b11245bace88f/src/hotspot/os_cpu/linux_arm/atomic_linux_arm.hpp#L149
Some Atomic implementations reach to StubRoutines for fallbacks:
https://github.com/openjdk/jdk/blob/9cf334fb6488188ea4236e5d156b11245bace88f/src/hotspot/os_cpu/linux_arm/os_linux_arm.cpp#L520
- backported by
-
JDK-8320076 Atomic gtest should run as TEST_VM to access VM capabilities
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk21u/67f5d7bb
-
Commit
openjdk/jdk/744f206f
-
Review
openjdk/jdk21u/339
-
Review
openjdk/jdk/16269
(1 links to)