[Bug target/104681] [9/10/11/12 Regression] ppc64le -mabi=ieeelongdouble ICE since r9-6460

[cvs-commit at gcc dot gnu.org]

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

--- 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:3885a122f817a1b6dca4a84ba9e020d5ab2060af

commit r12-7393-g3885a122f817a1b6dca4a84ba9e020d5ab2060af
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 can'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.