Remove has_max_index argument from G1BlockOffsetTablePart::block_at_or_preceding

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 18
    • Affects Version/s: 17
    • Component/s: hotspot
    • gc
    • b06

      That argument is always "true", so it can be removed.

      Potentially the third argument could also be folded as the code always passes "_next_offset_index-1".

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

              Created:
              Updated:
              Resolved: