[Bug c/109619] [12/13/14 Regression] ICE: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in fold_const_call_1, at fold-const-call.cc after r12-3278-g823685221de986.

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

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

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

commit r14-9613-gdbe9062ce070c861cd3fa6435187618413b1b3d1
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Thu Mar 21 16:29:20 2024 -0700

    Another ICE after conflicting types of redeclaration [PR109619]

    This another one of these ICE after error issues with the
    gimplifier and a fallout from r12-3278-g823685221de986af.
    This case happens when we are trying to fold memcpy/memmove.
    There is already code to try to catch ERROR_MARKs as arguments
    to the builtins so just need to change them to use error_operand_p
    which checks the type of the expression to see if it was an error mark
    also.

    Bootstrapped and tested on x86_64-linux-gnu with no regressions.

    gcc/ChangeLog:

            PR c/109619
            * builtins.cc (fold_builtin_1): Use error_operand_p
            instead of checking against ERROR_MARK.
            (fold_builtin_2): Likewise.
            (fold_builtin_3): Likewise.

    gcc/testsuite/ChangeLog:

            PR c/109619
            * gcc.dg/redecl-26.c: New test.

    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>