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/94420] [8/9/10 Regression] ICE error: insn does not satisfy its constraints
Date: Wed, 01 Apr 2020 17:01:23 +0000 [thread overview]
Message-ID: <bug-94420-4-rxnFMMTkRw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94420-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94420
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Segher Boessenkool <segher@gcc.gnu.org>:
https://gcc.gnu.org/g:032f2366a4cd57f781f2093d977b9cf9600c83b8
commit r10-7497-g032f2366a4cd57f781f2093d977b9cf9600c83b8
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Wed Apr 1 16:51:04 2020 +0000
rs6000: Make code questionably using r2 not ICE (PR94420)
The example code in the PR uses r2 (the TOC register) directly. In the
RTL generated for that, r2 is copied to some pseudo, and then cprop
propagates that into a "*tocref<mode>" insn, because nothing is
preventing it from doing that.
So, put the same condition in the insn condition for this as we will
later encounter in the constraint anyway, fixing this.
2020-04-01 Segher Boessenkool <segher@kernel.crashing.org>
PR target/94420
* config/rs6000/rs6000.md (*tocref<mode> for P): Add insn condition
on operands[1].
next prev parent reply other threads:[~2020-04-01 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 5:45 [Bug target/94420] New: " marxin at gcc dot gnu.org
2020-03-31 11:08 ` [Bug target/94420] [8/9/10 Regression] " jakub at gcc dot gnu.org
2020-03-31 13:53 ` segher at gcc dot gnu.org
2020-03-31 14:07 ` jakub at gcc dot gnu.org
2020-03-31 14:35 ` segher at gcc dot gnu.org
2020-03-31 14:36 ` segher at gcc dot gnu.org
2020-03-31 14:38 ` jakub at gcc dot gnu.org
2020-03-31 14:45 ` segher at gcc dot gnu.org
2020-03-31 14:46 ` segher at gcc dot gnu.org
2020-03-31 14:48 ` segher at gcc dot gnu.org
2020-04-01 8:59 ` rguenth at gcc dot gnu.org
2020-04-01 17:01 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-18 17:00 ` law at redhat dot com
2020-04-18 21:43 ` [Bug target/94420] [8/9 " segher at gcc dot gnu.org
2021-05-14 9:53 ` [Bug target/94420] [9 " jakub at gcc dot gnu.org
2021-06-01 8:17 ` rguenth at gcc dot gnu.org
2022-05-27 8:50 ` rguenth 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-94420-4-rxnFMMTkRw@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).