JDK-8253540 : InterpreterRuntime::monitorexit should be a JRT_LEAF function
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-09-23
- Updated: 2024-10-17
- Resolved: 2020-09-28
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 16 |
|---|
16 b18Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
That the monitor has already been unlocked, or is a null stacklock monitor has been already checked in the caller, so the code that makes it a JRT_ENTRY_NO_ASYNC is unnecessary. Making it a JRT_LEAF like the compiled method entries makes it safer. We know it can never safepoint and unintentionally install a async exception.
Comments
|