RFR: 8253540: InterpreterRuntime::monitorexit should be a JRT_LEAF function [v2]
Coleen Phillimore
coleenp at openjdk.java.net
Thu Sep 24 12:16:24 UTC 2020
> 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.
> Tested with tier1-6.
Coleen Phillimore has updated the pull request incrementally with one additional commit since the last revision:
8253540: InterpreterRuntime::monitorexit should be a JRT_LEAF function
-------------
Changes:
- all: https://git.openjdk.java.net/jdk/pull/320/files
- new: https://git.openjdk.java.net/jdk/pull/320/files/847442da..a54ae7cd
Webrevs:
- full: https://webrevs.openjdk.java.net/?repo=jdk&pr=320&range=01
- incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=320&range=00-01
Stats: 17 lines in 2 files changed: 15 ins; 0 del; 2 mod
Patch: https://git.openjdk.java.net/jdk/pull/320.diff
Fetch: git fetch https://git.openjdk.java.net/jdk pull/320/head:pull/320
PR: https://git.openjdk.java.net/jdk/pull/320
More information about the hotspot-dev
mailing list