G1: Use InvalidCSetIndex instead of UINT_MAX for "invalid" sentinel value of young_index_in_cset

XMLWordPrintable

    • gc
    • b12

      Current code hardcodes UINT_MAX for the "invalid" sentinel value of G1HeapRegion::_young_index_in_cset.

      The class already uses InvalidCSetIndex (with the same value) for the index_in_opt_cset.

      Reuse that one.

            Assignee:
            Thomas Schatzl
            Reporter:
            Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: