RFR: 8253540: InterpreterRuntime::monitorexit should be a JRT_LEAF function [v3]
Coleen Phillimore
coleenp at openjdk.java.net
Fri Sep 25 22:15:10 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:
make calls through call_VM_leaf
-------------
Changes:
- all: https://git.openjdk.java.net/jdk/pull/320/files
- new: https://git.openjdk.java.net/jdk/pull/320/files/a54ae7cd..083f345d
Webrevs:
- full: https://webrevs.openjdk.java.net/?repo=jdk&pr=320&range=02
- incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=320&range=01-02
Stats: 70 lines in 10 files changed: 6 ins; 36 del; 28 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