[lilliput-jdk17u:lilliput] RFR: 8304331: [Lilliput/JDK17] Fix RTM locking
Aleksey Shipilev
shade at openjdk.org
Thu Mar 16 13:10:50 UTC 2023
On Thu, 16 Mar 2023 10:01:42 GMT, Roman Kennke <rkennke at openjdk.org> wrote:
> Some RTM locking tests are currently failing:
>
> compiler/rtm/cli/TestUseRTMLockingOptionWithBiasedLocking.java
> compiler/rtm/locking/TestRTMRetryCount.java
> compiler/rtm/locking/TestRTMTotalCountIncrRate.java
> compiler/rtm/locking/TestUseRTMAfterLockInflation.java
> compiler/rtm/locking/TestUseRTMForInflatedLocks.java
> compiler/rtm/locking/TestUseRTMForStackLocks.java
> compiler/rtm/method_options/TestUseRTMLockElidingOption.java
>
> Most are because there's a jmpb in UseRTMLocking parts that fails because of longer locking code with Lilliput. One test is failing because it checks a warning message when somebody tries +UseBiasedLocking together with RTM locking, but Lilliput forces biased locking to be off, so the warning never appears. I problem-listed that test.
>
> Testing:
> - [x] all tests listed above
Marked as reviewed by shade (Reviewer).
test/hotspot/jtreg/ProblemList.txt line 180:
> 178: gc/arguments/TestCompressedClassFlags.java 1234567 generic-all
> 179:
> 180: # Dispabled because Lilliput forces -UseBiasedLocking
Unrelated, but typo: "Dispabled"
-------------
PR: https://git.openjdk.org/lilliput-jdk17u/pull/12
More information about the lilliput-dev
mailing list