JDK-8166607 : G1 needs klass_or_null_acquire
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2016-09-23
  • Updated: 2021-02-05
  • Resolved: 2016-11-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9 Other
8u301Fixed 9 b150Fixed openjdk8u292Fixed
Related Reports
Blocks :  
JDK-8166663 - Simplify oops_on_card_seq_iterate_careful
Blocks :  
JDK-8166583 - Add oopDesc::klass_or_null_acquire()
Relates :  
JDK-8162928 - Micro-optimizations in scanning the remembered sets
Relates :  
JDK-8071280 - Specialize HeapRegion::oops_on_card_seq_iterate_careful() for use during concurrent refinement and updating the rset
Description
Some of the places where G1 uses klass_or_null really should be using klass_or_null_acquire, in order to ensure the successful read of the klass preceeds later reads that are dependent on it.