[Bug middle-end/112336] fsanitize=address vs _BitInt with a non-mode size (smaller than max mode size)

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

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

--- Comment #5 from CVS 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:f9982ef4f55bd3a63745e03ac6d68b4a92fa8bce

commit r14-5776-gf9982ef4f55bd3a63745e03ac6d68b4a92fa8bce
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Nov 23 12:59:54 2023 +0100

    expr: Fix &bitint_var handling in initializers [PR112336]

    As the following testcase shows, we ICE when trying to emit ADDR_EXPR of
    a bitint variable which doesn't have mode width.
    The problem is in the EXTEND_BITINT stuff which makes sure we treat the
    padding bits on memory reads from user bitint vars as undefined.
    When expanding ADDR_EXPR on such vars inside outside of initializers,
    expand_expr_addr* uses EXPAND_CONST_ADDRESS modifier and EXTEND_BITINT
    does nothing, but in initializers it keeps using EXPAND_INITIALIZER
    modifier.  So, we need to treat EXPAND_INITIALIZER the same as
    EXPAND_CONST_ADDRESS for this regard.

    2023-11-23  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/112336
            * expr.cc (EXTEND_BITINT): Don't call reduce_to_bit_field_precision
            if modifier is EXPAND_INITIALIZER.

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