-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 23, 24
-
b04
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8337186 | 23.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8337191 | 21.0.5 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8337349 | 17.0.13 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
Right now, the CodeCache_lock is placed at their call site, which is not very obvious and readable. Let's move the lock inside the methods.
- backported by
-
JDK-8337186 Shenandoah: Move CodeCache_lock close to its use in ShenandoahConcurrentNMethodIterator
- Resolved
-
JDK-8337191 Shenandoah: Move CodeCache_lock close to its use in ShenandoahConcurrentNMethodIterator
- Resolved
-
JDK-8337349 Shenandoah: Move CodeCache_lock close to its use in ShenandoahConcurrentNMethodIterator
- Resolved
- links to
-
Commit openjdk/jdk/4ebb7712
-
Commit(master) openjdk/jdk17u-dev/efee05f4
-
Commit(master) openjdk/jdk21u-dev/4cab9a4b
-
Commit(master) openjdk/jdk23u/6ad484a4
-
Review openjdk/jdk/19859
-
Review(master) openjdk/jdk17u-dev/2742
-
Review(master) openjdk/jdk21u-dev/868
-
Review(master) openjdk/jdk23u/33