RFR: 8327250: assert(!method->is_old()) failed: Should not be installing old methods
Coleen Phillimore
coleenp at openjdk.org
Wed Apr 10 12:56:17 UTC 2024
When the [JDK-8322630](https://bugs.openjdk.org/browse/JDK-8322630) ICStubs and safepoints were removed, a check to ignore redefined methods was removed (is_old() check), but that check was in the wrong place. The LinkResolver finds a Method to call through resolution and selection and saves that Method in the returned CallInfo. The CallInfo object is temporary until the method is stored somewhere "safe", ie somewhere redefinition knows how to replace the method with a new method or deoptimize. At any safepoint, the Method could be redefined, so the CallInfo return should check for old methods and only return the equivalent new method.
This change removes the one check in the interpreter and moves it to the CallInfo accessors.
Tested with the failing test case with options: "-Xcomp -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:TieredStopAtLevel=2", all vmTestBase/nsk/jvmti tests with these options, and ran tiers 1-8.
-------------
Commit messages:
- 8327250: assert(!method->is_old()) failed: Should not be installing old methods
Changes: https://git.openjdk.org/jdk/pull/18719/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=18719&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8327250
Stats: 33 lines in 3 files changed: 24 ins; 4 del; 5 mod
Patch: https://git.openjdk.org/jdk/pull/18719.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/18719/head:pull/18719
PR: https://git.openjdk.org/jdk/pull/18719
More information about the hotspot-runtime-dev
mailing list