Shenandoah: Move CodeCache_lock close to its use in ShenandoahConcurrentNMethodIterator

XMLWordPrintable

    • gc
    • b04

        ShenandoahConcurrentNMethodIterator requires CodeCache_lock at begin and end of iteration.

        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.

              Assignee:
              Zhengyu Gu
              Reporter:
              Zhengyu Gu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: