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 B137538618BD; Tue, 14 Jul 2020 14:04:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B137538618BD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1594735455;
 bh=pCiUVtv0ZLdlBjHu6qRmRHFy85NluPf1uF/JW7Djsw0=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=EBlX6rPNqbxt4vRottD1TMMHWlSuSkadYR2aVnihTXapXsklcEspIsZO93te2gniG
 FcC2IQrengLyUNS2zTmGPuUdcciqCeu3E7BuOo7O7THo0KmbIR3ZKDhafj91HnoF8h
 hS3SLdSql78W/vkUQarPuxV8tbR0X0dP2UbSj4Lg=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/96194] [10/11 Regression] ICE in assign_temp, at
 function.c:984 during RTL pass: expand
Date: Tue, 14 Jul 2020 14:04:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.1.1
X-Bugzilla-Keywords: 
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.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-96194-4-JEKd8otPBx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96194-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96194-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: <https://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: Tue, 14 Jul 2020 14:04:15 -0000

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

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

commit r10-8493-gde70758207a6b2d8d3d6bbd3fc564ca736ed094f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Jul 14 16:01:11 2020 +0200

    expr: Unbreak build of mesa [PR96194]

    > > The store to the whole of each volatile object was picked apart
    > > like there had been an individual assignment to each of the
    > > fields.  Reads were added as part of that; see PR for details.
    > > The reads from volatile memory were a clear bug; individual
    > > stores questionable.  A separate patch clarifies the docs.

    This breaks building of mesa on both the trunk and 10 branch.

    The problem is that the middle-end may never create temporaries of non-=
POD
    (TREE_ADDRESSABLE) types, those can be only created when the language s=
ays
    so and thus only the FE is allowed to create those.

    This patch just reverts the behavior to what we used to do before for t=
he
    stores to volatile non-PODs.  Perhaps we want to do something else, but
    definitely we can't create temporaries of the non-POD type.  It is up to
    discussions on what should happen in those cases.

    2020-07-14  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/96194
            * expr.c (expand_constructor): Don't create temporary for store=
 to
            volatile MEM if exp has an addressable type.

            * g++.dg/opt/pr96194.C: New test.

    (cherry picked from commit b1d389d60d1929c7528ef984925ea010e3bf2c1a)=