Shenandoah: consider walking CLDG without _claim_strong

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: 8-shenandoah, 11-shenandoah, 14, 15
    • Component/s: hotspot
    • gc

      As the more complicated followup for JDK-8246097, we might even consider walking the CLDG without _claim_strong and avoid clearing the marks before the walk. The only problem is that we need to make sure every path does _claim_none. And there are, unfortunately, paths through shared OopIterateClosures that default to _claim_strong, for example MetadataVisitingOopIterateClosure.

      POC:
       http://cr.openjdk.java.net/~shade/8246101/8246101-poc.patch

            Assignee:
            Unassigned
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: