RFR: 8364650: G1: Use InvalidCSetIndex instead of UINT_MAX for "invalid" sentinel value of young_index_in_cset
Thomas Schatzl
tschatzl at openjdk.org
Thu Aug 21 09:22:01 UTC 2025
On Mon, 18 Aug 2025 07:08:20 GMT, Ivan Walulya <iwalulya at openjdk.org> wrote:
>> Hi all,
>>
>> please review this small change to use `InvalidCSetIndex` instead of hardcoded `UINT_MAX` for `G1HeapRegion::_young_index_in_cset`. Just reuse the existing value that is already in use for `_index_in_opt_cset`.
>>
>> Testing: compilation, gha
>>
>> Thanks,
>> Thomas
>
> Marked as reviewed by iwalulya (Reviewer).
Thanks @walulyai @albertnetymk for your reviews
-------------
PR Comment: https://git.openjdk.org/jdk/pull/26651#issuecomment-3209695664
More information about the hotspot-gc-dev
mailing list