public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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/11/12 Regression] ppc64le -mabi=ieeelongdouble ICE since r9-6460
Date: Fri, 25 Feb 2022 18:02:10 +0000	[thread overview]
Message-ID: <bug-104681-4-9kmyUU1Noz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104681-4@http.gcc.gnu.org/bugzilla/>

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.

  parent reply	other threads:[~2022-02-25 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 20:29 [Bug target/104681] New: " jakub at gcc dot gnu.org
2022-02-24 20:30 ` [Bug target/104681] " jakub at gcc dot gnu.org
2022-02-25 11:55 ` jakub at gcc dot gnu.org
2022-02-25 15:40 ` segher at gcc dot gnu.org
2022-02-25 15:43 ` jakub at gcc dot gnu.org
2022-02-25 17:05 ` segher at gcc dot gnu.org
2022-02-25 18:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-25 18:03 ` [Bug target/104681] [9/10/11 " jakub at gcc dot gnu.org
2022-03-29  5:53 ` cvs-commit at gcc dot gnu.org
2022-03-30  8:15 ` [Bug target/104681] [9/10 " jakub at gcc dot gnu.org
2022-05-10  8:24 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:25 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:36 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104681-4-9kmyUU1Noz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).