JDK-8248359 : Update JVMCI
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11,16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-06-25
- Updated: 2022-02-06
- Resolved: 2020-07-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 11 | JDK 16 |
|---|---|
| 11.0.9-oracleFixed | 16 b05Fixed  |
Description
This issue is to port a number of improvements to JVMCI from jvmci-8: * Move C++ state and functionality associated with a HotSpotJVMCIRuntime Java object into its peer JVMCIRuntime C++ object (e.g., the _shared_library_javavm moves from being a static field in JVMCIEnv to an instance field in JVMCIRuntime). * The management of JNI globals handles and Metadata handles passed to JVMCI Java code should also be moved to JVMCIRuntime. * Introduce tracing of low frequency JVMCIRuntime lifetime events (e.g. JVMCIRuntime lifetime phase events) at less verbose trace level. * Trace high frequency JVMCI events (e.g. CompilerToVM calls) at more verbose trace level. * Detect unsupported jvmci.* system properties and use fuzzy matching for an error message suggesting closely matching supported properties. * Improve javadoc for HotSpotJVMCIRuntime.attachCurrentThread. * Reduce calls to JavaThread::current() in conjunction with JNIAccessMark.
Comments
|