JDK-8184181 : Use oopDesc::cas_set_mark() instead of raw CAS when accessing oop header
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2017-07-11
  • Updated: 2019-05-22
  • Resolved: 2017-07-17
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 10
10 b21Fixed
Related Reports
Relates :  
JDK-8163329 - JEP 304: Garbage Collector Interface
Comments
Let's see what the triage team does with it...
11-07-2017
Good question. I am undecided. One one hand, it mostly helps the GC. For example, Shenandoah wants to insert the right barriers and or sanity checks when accessing the mark word. On the other hand, it only affects code all over the runtime (e.g. biasedlocking and synchonizer). At the very minimum, it is a nice cleanup for runtime code. Your call. :-)
11-07-2017
Does this bug belong in hotspot/gc instead of hotspot/runtime?
11-07-2017