Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8239868

Shenandoah: ditch C2 node limit adjustments

    XMLWordPrintable

Details

    • gc
    • b12

    Backports

      Description

        We have the block added to Shenandoah arguments code that adjust MaxNodeLimit and friends (predates inclusion of Shenandoah into mainline):
         https://mail.openjdk.java.net/pipermail/shenandoah-dev/2018-August/006983.html

        At the time, it was prompted by observing that lots of barriers everywhere really needed to have this limit bumped. Today, with simplified LRB scheme, more simple LRB due to SFX, etc, we do not need this.

        The change above used ShenandoahCompileCheck, which made it into upstream code under generic AbortVMOnCompilationFailure. With that, I was able to verify that dropping the block does not yield compilation failures due to exceeded node budget on hotspot_gc_shenandoah, specjvm2008, specjbb2015. Performance numbers are also not affected (as expected).

        Therefore, the adjustment can be removed.

        Attachments

          Issue Links

            Activity

              People

                shade Aleksey Shipilev
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: