[Bug middle-end/113410] ICE: in maybe_check_access_sizes, at gimple-ssa-warn-access.cc:3423 with _BitInt() used as array length

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113410

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:a98a24ac65c1a0ee598e5b54d9e4c921a9744a08

commit r14-8185-ga98a24ac65c1a0ee598e5b54d9e4c921a9744a08
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 17 13:57:07 2024 +0100

    gimple-ssa-warn-access: Cast huge params to sizetype before using them in
maybe_check_access_sizes [PR113410]

    WHen a VLA is created with some very high precision size expression
    (say __int128, or _BitInt(65535) etc.), we cast it to sizetype, because
    we can't have arrays longer than what can be expressed in sizetype.

    But the maybe_check_access_sizes code when trying to determine ranges
    wasn't doing this but was using fixed buffers for the sizes.  While
    __int128 could still be handled (fit into the buffers), obviously
    arbitrary _BitInt parameter ranges can't, they can be in the range of
    up to almost 20KB per number.  It doesn't make sense to print such
    ranges though, no array can be larger than sizetype precision, and
    ranger's range_of_expr can handle NOP_EXPRs/CONVERT_EXPRs wrapping a
    PARM_DECL just fine, so the following patch just casts the excessively
    large counters for the range determination purposes to sizetype.

    2024-01-17  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/113410
            * gimple-ssa-warn-access.cc
(pass_waccess::maybe_check_access_sizes):
            If access_nelts is integral with larger precision than sizetype,
            fold_convert it to sizetype.

            * gcc.dg/bitint-72.c: New test.