From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 95E043937431; Mon, 16 Mar 2020 21:59:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 95E043937431
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1584395970;
 bh=+jqKV78Vh+T1c/ZsbIq8dKVHg2p4tmCIaoRANUNeI/8=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=VFxkfsLbayyZoTuJRB+S0xj0wVlnA+t5BtTDPZsri/kFDV8GFO+HRpO+wKPN68PwV
 GnwfnHOPTFq7IexADctqpunpZMOeWo7sYz1+j78q8MTLZTnB1kOM8aEDsIn+AVPaPV
 1msSjhA49YBsFRxGzER6o0WEWrwZWGB/RPQCmET0=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94179] [10 Regression] ICE in gimplify_expr, at
 gimplify.c:14399 since r10-7127-gcb99630f254aaec6
Date: Mon, 16 Mar 2020 21:59:30 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-94179-4-LC907wG5Ei@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94179-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94179-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <http://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2020 21:59:30 -0000

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

--- Comment #4 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:c015ff8ccaf3ee8e4f6393679ed790ed0df92873

commit r10-7198-gc015ff8ccaf3ee8e4f6393679ed790ed0df92873
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Mar 16 22:58:41 2020 +0100

    c: Handle MEM_REF in c_fully_fold* [PR94179]

    The recent match.pd changes can generate a MEM_REF which can be seen by=
 the
    C FE folding routines.  Unlike the C++ FE, they weren't expected in the=
 C
FE
    yet.  MEM_REF should be handled like INDIRECT_REF, except that it has t=
wo
    operands rather than just one and that we should preserve the type of t=
he
    second operand.  Given that it already has to be an INTEGER_CST with
pointer
    type, I think we are fine, the recursive call should return the INTEGER=
_CST
    unmodified and STRIP_TYPE_NOPS will not strip anything.

    2020-03-16  Jakub Jelinek  <jakub@redhat.com>

            PR c/94179
            * c-fold.c (c_fully_fold_internal): Handle MEM_REF.

            * gcc.c-torture/compile/pr94179.c: New test.=