JDK-8234086 : VM operation can be simplified
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-11-13
- Updated: 2019-12-10
- Resolved: 2019-11-29
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.
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 14 |
|---|
14 b26Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
CMS was using some of the VM ops more complicated features. Now that CMS is removed we no longer have any use for them. Other GCs handle this work without using complicated VM op features and do not need this functionality, which is a better approach. This means all VM ops can be stack allocated and synchronous. We thus remove concurrent (non-safepoint heap allocated) and asynchronous (safepoint heap allocated) ops. There are some future features which could utilize concurrent handshake operations. These would mainly be single Java thread targeted handshakes and thus would not use a VM op. That assumes we have Thread->JavaThread handshake support. Currently we always do Thread->VM Thread (via VM op)->JavaThread.
Comments
|