public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109987] ICE in in rs6000_emit_le_vsx_store on ppc64le with -Ofast -mno-power8-vector
Date: Mon, 29 May 2023 01:29:18 +0000 [thread overview]
Message-ID: <bug-109987-4-AQj99QH3tc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109987-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109987
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Keywords| |ice-on-valid-code
CC| |bergner at gcc dot gnu.org,
| |linkw at gcc dot gnu.org,
| |segher at gcc dot gnu.org
Last reconfirmed| |2023-05-29
--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
Confirmed, it's similar to what the issue was found in PR103627 #c4, previously
I made a patch to make MMA feature require power9-vector, see
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587310.html. But Segher
thought power9-vector is a workaround option, we should make it go away, so
just guard it under vsx, see his comment
https://gcc.gnu.org/pipermail/gcc-patches/2022-January/589303.html.
Unfortunately this issue is specified another workaround option
-mno-power8-vector, I think we probably need to put -mpower{8,9}-vector removal
in a high priority.
next prev parent reply other threads:[~2023-05-29 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:05 [Bug target/109987] New: " jamborm at gcc dot gnu.org
2023-05-29 1:29 ` linkw at gcc dot gnu.org [this message]
2024-01-09 2:07 ` [Bug target/109987] " linkw at gcc dot gnu.org
2024-01-10 8:13 ` linkw at gcc dot gnu.org
2024-03-26 6:23 ` pinskia 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-109987-4-AQj99QH3tc@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).