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/113950] PowerPC, ICE with -O1 or higher compiling __builtin_vsx_splat_2di test case
Date: Thu, 21 Mar 2024 09:55:36 +0000	[thread overview]
Message-ID: <bug-113950-4-otM7opGSl1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113950-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by jeevitha <jeevitha@gcc.gnu.org>:

https://gcc.gnu.org/g:27eb6e81e6e578da9f9947d3f96c0fa58971fe7f

commit r13-8474-g27eb6e81e6e578da9f9947d3f96c0fa58971fe7f
Author: Jeevitha <jeevitha@linux.ibm.com>
Date:   Wed Mar 20 23:34:46 2024 -0500

    rs6000: Don't ICE when compiling the __builtin_vsx_splat_2di [PR113950]

    When we expand the __builtin_vsx_splat_2di built-in, we were allowing
immediate
    value for second operand which causes an unrecognizable insn ICE. Even
though
    the immediate value was forced into a register, it wasn't correctly
assigned
    to the second operand. So corrected the assignment of op1 to operands[1].

    2024-03-07  Jeevitha Palanisamy  <jeevitha@linux.ibm.com>

    gcc/
            PR target/113950
            * config/rs6000/vsx.md (vsx_splat_<mode>): Correct assignment to
operand1
            and simplify else if with else.

    gcc/testsuite/
            PR target/113950
            * gcc.target/powerpc/pr113950.c: New testcase.

    (cherry picked from commit fa0468877869f52b05742de6deef582e4dd296fc)

  parent reply	other threads:[~2024-03-21  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 23:43 [Bug target/113950] New: " carll at gcc dot gnu.org
2024-02-16  0:00 ` [Bug target/113950] " bergner at gcc dot gnu.org
2024-02-23  1:35 ` bergner at gcc dot gnu.org
2024-03-07 14:18 ` cvs-commit at gcc dot gnu.org
2024-03-15 20:36 ` bergner at gcc dot gnu.org
2024-03-21  9:55 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-01  5:58 ` cvs-commit at gcc dot gnu.org
2024-05-16 13:58 ` jeevitha at gcc dot gnu.org
2024-05-16 14:02 ` jeevitha at gcc dot gnu.org
2024-05-16 15:04 ` shivam98.tkg at gmail dot com

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-113950-4-otM7opGSl1@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).