From: Hans-Peter Nilsson <hp@axis.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH] gen_reload: Correct parameter for fatal_insn call
Date: Wed, 15 Feb 2023 01:18:14 +0100 [thread overview]
Message-ID: <20230215001814.F3BAB2042C@pchp3.se.axis.com> (raw)
Committed as obvious. Also, I wrote the neighboring code
- apparently including that line...
-- >8 --
Observed when disabling LEGITIMIZE_RELOAD_ADDRESS for
cris-elf: the current code doesn't handle the post-cc0
parallel-with-clobber-of-cc0 sets, dropping down into the
fatal_insn call. Following the code, it's obvious that the
variable "set" is always NULL at the call. The intended
parameter is "in".
* reload1.cc (gen_reload): Correct rtx parameter for fatal_insn
"failure trying to reload" call.
---
gcc/reload1.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/reload1.cc b/gcc/reload1.cc
index 6fe22d8b81f9..7dcef50437b8 100644
--- a/gcc/reload1.cc
+++ b/gcc/reload1.cc
@@ -8606,7 +8606,7 @@ gen_reload (rtx out, rtx in, int opnum, enum reload_type type)
return insn;
}
- fatal_insn ("failure trying to reload:", set);
+ fatal_insn ("failure trying to reload:", in);
}
/* If IN is a simple operand, use gen_move_insn. */
else if (OBJECT_P (in) || GET_CODE (in) == SUBREG)
--
2.30.2
reply other threads:[~2023-02-15 0:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230215001814.F3BAB2042C@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@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).