JDK-8216371 : [JVMCI] remove HotSpotJVMCIMetaAccessContext
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 13
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- Submitted: 2019-01-08
- Updated: 2019-05-01
- Resolved: 2019-05-01
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 13 |
|---|
13Resolved  |
Related Reports
|
Blocks :
|
|
|
Duplicate :
|
Description
HotSpotJVMCIMetaAccessContext was designed to be a thread local context analogous to ciEnv. However, it turned out to be untenable for performance. As such, there is only a single global instance HotSpotJVMCIMetaAccessContext which make this class is kind of vestigial. Moving all the state into HotSpotJVMCIRuntime would make sense.
Comments
|