-
Bug
-
Resolution: Fixed
-
P3
-
12, 13
-
b22
-
x86
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8228953 | 12u-cpu | Boris Ulasevich | P3 | Resolved | Fixed | master |
JDK-8224189 | 12.0.2 | Boris Ulasevich | P3 | Resolved | Fixed | b03 |
The simple application (attached) shows broken volatile long field.
Reproduced on 32-bit x86, interpreter VM mode only.
The issue came withJDK-8202201 update: MO_RELAXED atomic access_store_at parmeter was lost, it breaks the atomicity.
jcstress shows it is not the only problem for x86_32: jcstress.jar -t IntLongTest fails massively (in compiler mode) - seeJDK-8223557 for this issue.
Reproduced on 32-bit x86, interpreter VM mode only.
The issue came with
jcstress shows it is not the only problem for x86_32: jcstress.jar -t IntLongTest fails massively (in compiler mode) - see
- backported by
-
JDK-8224189 volatile long field corruption on x86_32
- Resolved
-
JDK-8228953 volatile long field corruption on x86_32
- Resolved
- relates to
-
JDK-8202201 All oop stores in the x64 interpreter are treated as volatile when using G1
- Resolved
-
JDK-8223557 jcstress fails on 32-bit x86
- Closed