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/98959] ICE in extract_constrain_insn, at recog.c:2670
Date: Mon, 08 Mar 2021 18:24:04 +0000 [thread overview]
Message-ID: <bug-98959-4-jQiX7yJhri@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98959-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98959
--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:cb25dea3ef2c7768007bffc56f0e31e1c42b44e2
commit r11-7558-gcb25dea3ef2c7768007bffc56f0e31e1c42b44e2
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Mon Mar 8 12:20:41 2021 -0600
rs6000: Fix invalid splits when using Altivec style addresses [PR98959]
The rs6000_emit_le_vsx_* functions assume they are not passed an Altivec
style "& ~16" address. However, some of our expanders and splitters do
not verify we do not have an Altivec style address before calling those
functions, leading to an ICE. The solution here is to guard the expanders
and splitters to ensure we do not call them if we're given an Altivec style
address.
2021-03-08 Peter Bergner <bergner@linux.ibm.com>
gcc/
PR target/98959
* config/rs6000/rs6000.c (rs6000_emit_le_vsx_permute): Add an
assert
to ensure we do not have an Altivec style address.
* config/rs6000/vsx.md (*vsx_le_perm_load_<mode>): Disable if
passed
an Altivec style address.
(*vsx_le_perm_store_<mode>): Likewise.
(splitters after *vsx_le_perm_store_<mode>): Likewise.
(vsx_load_<mode>): Disable special expander if passed an Altivec
style address.
(vsx_store_<mode>): Likewise.
gcc/testsuite/
PR target/98959
* gcc.target/powerpc/pr98959.c: New test.
next prev parent reply other threads:[~2021-03-08 18:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 18:52 [Bug target/98959] New: " marxin at gcc dot gnu.org
2021-02-03 18:52 ` [Bug target/98959] " marxin at gcc dot gnu.org
2021-02-04 11:44 ` jakub at gcc dot gnu.org
2021-02-04 12:19 ` marxin at gcc dot gnu.org
2021-02-04 13:20 ` marxin at gcc dot gnu.org
2021-02-04 13:20 ` marxin at gcc dot gnu.org
2021-02-04 13:23 ` marxin at gcc dot gnu.org
2021-02-04 13:24 ` marxin at gcc dot gnu.org
2021-02-04 16:33 ` bergner at gcc dot gnu.org
2021-02-04 17:01 ` bergner at gcc dot gnu.org
2021-02-04 17:08 ` marxin at gcc dot gnu.org
2021-02-04 18:18 ` jakub at gcc dot gnu.org
2021-02-04 19:29 ` bergner at gcc dot gnu.org
2021-02-04 19:37 ` bergner at gcc dot gnu.org
2021-02-05 0:13 ` bergner at gcc dot gnu.org
2021-02-07 22:06 ` wschmidt at gcc dot gnu.org
2021-02-11 22:28 ` bergner at gcc dot gnu.org
2021-02-11 23:56 ` bergner at gcc dot gnu.org
2021-02-11 23:59 ` bergner at gcc dot gnu.org
2021-02-12 20:51 ` bergner at gcc dot gnu.org
2021-03-08 18:24 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-10 19:09 ` bergner at gcc dot gnu.org
2021-03-10 21:31 ` segher at gcc dot gnu.org
2021-03-10 23:48 ` cvs-commit at gcc dot gnu.org
2021-03-11 0:03 ` bergner 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-98959-4-jQiX7yJhri@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).