JDK-8236035 : refactor ObjectMonitor::set_owner() and _owner field setting
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8u72,9,14,15
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-12-16
  • Updated: 2020-02-10
  • Resolved: 2020-02-05
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 15
15 b09Fixed
Related Reports
Relates :  
JDK-8238174 - migrate ObjectMonitor::_owner field away from C++ volatile semantics
Description
Setting the ObjectMonitor::_owner field is more complicated
than your typical set_owner() abstraction.

This subtask is split off from the Async Monitor Deflation project
that is tracked by JDK-8153224.
Comments
Changeset: 8ff24c55 Author: Daniel D. Daugherty <dcubed@openjdk.org> Date: 2020-02-05 11:39:52 +0000 URL: https://git.openjdk.java.net/panama-foreign/commit/8ff24c55
07-02-2020
URL: https://hg.openjdk.java.net/jdk/jdk/rev/00470b6c0eaf User: dcubed Date: 2020-02-05 16:41:12 +0000
05-02-2020