public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner 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: Fri, 15 Mar 2024 20:36:17 +0000	[thread overview]
Message-ID: <bug-113950-4-ggak1Soo1H@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 #4 from Peter Bergner <bergner at gcc dot gnu.org> ---
The bogus vsx_splat_<mode> code goes all the way back to GCC 8, so we need
backports to the open release branches (GCC 13, 12, 11).

  parent reply	other threads:[~2024-03-15 20:36 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 [this message]
2024-03-21  9:55 ` cvs-commit at gcc dot gnu.org
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-ggak1Soo1H@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).