The _finger field of G1ConcurrentMark is part of a lock-free protocol, yet is missing a volatile specifier, which leads to less robust behavior.
The behavior is more robust with volatiles turned on, and our helmets should always be on.
This is related toJDK-8033552, but was split out due to the large size of the work being done there.
The behavior is more robust with volatiles turned on, and our helmets should always be on.
This is related to
- blocks
-
JDK-8033552 Fix missing missing volatile specifiers in CAS operations in GC code
-
- Resolved
-
- relates to
-
-
- Resolved
-