JDK-8221766 : Load-reference barriers for Shenandoah
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 8-shenandoah,11-shenandoah,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-04-01
  • Updated: 2019-10-07
  • Resolved: 2019-04-04
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 13
13 b16Fixed
Related Reports
Blocks :  
JDK-8222838 - Shenandoah: SEGV on accessing cset bitmap for NULL ptr
Blocks :  
JDK-8222766 - Shenandoah: streamline post-LRB CAS barrier (x86)
Blocks :  
JDK-8222786 - Shenandoah get_barrier_strength should accept all shapes of (Weak)CAS reference barriers
Blocks :  
JDK-8222129 - Shenandoah: Missing CompareAndSwapP/N case in get_barrier_strength()
Blocks :  
JDK-8225048 - Shenandoah x86_32 support
Relates :  
JDK-8225171 - Remove leftovers in shenandoahBarrierSetC1.cpp
Relates :  
JDK-8230470 - Shenandoah doesn't need change from JDK-8212610 anymore
Relates :  
JDK-8206457 - Code paths from oop_iterate() must use barrier-free access
Relates :  
JDK-8224525 - Shenandoah: Eliminate shenandoah verifier's side-effects
Relates :  
JDK-8224667 - Shenandoah: Post-LRB cleanup
Relates :  
JDK-8224584 - Shenandoah: Eliminate forwarding pointer word
Relates :  
JDK-8224522 - Shenandoah should apply barriers on deoptimization
Relates :  
JDK-8223448 - Shenandoah disabled barriers blocks omit LRB
Relates :  
JDK-8231946 - Remove obsolete and unused ShenandoahVerifyObjectEquals flag
Sub Tasks
JDK-8225516 :  
Release Note: Load reference barriers for Shenandoah - Closed
Description
Instead of ensuring the proper read- or write-invariant at obj and primitive store-sites, we can ensure strong invariant at object load sites. This would simplify lots of code, make optimizations much simpler and improve overall performance.