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 C2A5F385AC22; Wed, 11 May 2022 06:25:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C2A5F385AC22
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104681] [9/10 Regression] ppc64le -mabi=ieeelongdouble
 ICE since r9-6460
Date: Wed, 11 May 2022 06:25:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 12.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: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-104681-4-phMwEU7SIX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104681-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2022 06:25:24 -0000

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

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

https://gcc.gnu.org/g:5c742d9a7e217746de961da20a39f04e5ec1df25

commit r9-10135-g5c742d9a7e217746de961da20a39f04e5ec1df25
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Feb 25 18:58:48 2022 +0100

    rs6000: Use rs6000_emit_move in movmisalign<mode> expander [PR104681]

    The following testcase ICEs, because for some strange reason it decides=
 to
use
    movmisaligntf during expansion where the destination is MEM and source =
is
    CONST_DOUBLE.  For normal mov<mode> expanders the rs6000 backend uses
    rs6000_emit_move to ensure that if one operand is a MEM, the other is a=
 REG
    and a few other things, but for movmisalign<mode> nothing enforced this.
    The middle-end documents that movmisalign<mode> shouldn't fail, so we c=
an't
    force that through predicates or condition on the expander.

    2022-02-25  Jakub Jelinek  <jakub@redhat.com>

            PR target/104681
            * config/rs6000/vector.md (movmisalign<mode>): Use
rs6000_emit_move.

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

    (cherry picked from commit 3885a122f817a1b6dca4a84ba9e020d5ab2060af)=