| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8362744 | 17.0.17-oracle | Daniel Daugherty | P4 | Resolved | Fixed | b03 |
The oop class and its subclasses are made more complicated by the presence of volatile qualified member functions and parameters. Those overloads exist to support operations on volatile oop values. But such values exist as the conventional mechanism for noting a variable is accessed by multiple threads and needs special handling. The intended semantics for these bare volatile variable accesses is really relaxed atomic, and it would be better to actually use such. Doing so would eliminate the need for the volatile qualifications in the member functions.
- backported by
-
JDK-8362744 Remove volatile-qualified member functions and parameters from oop class
-
- Resolved
-
- relates to
-
JDK-8245942 Shenandoah: x86_32 builds fail after JDK-8245594
-
- Closed
-
-
JDK-8243326 Cleanup use of volatile in taskqueue code
-
- Resolved
-
-
-
- Resolved
-