JDK-8210498 : nmethod entry barriers
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9,10,11,12
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-09-07
- Updated: 2022-10-03
- Resolved: 2018-10-16
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 12 |
|---|
12 b16Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
In order to implement concurrent class unloading, a mechanism will be required to arm nmethods in a safepoint such that the first entry into an nmethod after the pause triggers a barrier before continuing. The barrier will be used for: * Patching immediate oops, and keeping phantomly reachable oops alive through the nmethod entry * Cleaning IC caches that are potentially stale after class unloading * Detecting entries through stale IC caches during unloading
Comments
|