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.
After JDK-8331714, we don't need the Generational Z kludge that works around the lock ranking problem with (now gone) OopMapCacheAlloc_lock.
Comments
A pull request was submitted for review.
Branch: master
URL: https://git.openjdk.org/jdk/pull/19114
Date: 2024-05-07 09:00:47 +0000
08-01-2025
A pull request was submitted for review.
Branch: master
URL: https://git.openjdk.org/jdk22u/pull/232
Date: 2024-05-31 06:06:54 +0000
09-07-2024
[jdk21u-fix-request] Approval Request from Xiaolong Peng
Backport [JDK-8331771](https://bugs.openjdk.org/browse/JDK-8331771) to remove OopMapCacheAlloc_lock ordering workaround in ZGC, the blocker issue JDK-8331714 has already been backported to jdk21. Applies cleanly after merging master into backport branch; Risk should be on the lower side since change of issue is fairly simple.
31-05-2024
[jdk22u-fix-request] Approval Request from Xiaolong Peng
Backport to remove OopMapCacheAlloc_lock ordering workaround in ZGC, the blocker issue JDK-8331714 has already been backported to jdk22. Applies cleanly, except there was code conflicts caused by the renamings from issue JDK-8331573, I manually resolved those conflicts(It may not worth to backport JDK-8331573 since jdk22 is ramping down); Risk should be on the lower side since change of issue is fairly simple.
31-05-2024
A pull request was submitted for review.
URL: https://git.openjdk.org/jdk21u-dev/pull/626
Date: 2024-05-31 06:23:07 +0000