From: Oleg Endo <oleg.endo@t-online.de>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [SH][committed] Fix PR 111001
Date: Mon, 23 Oct 2023 22:28:15 +0900 [thread overview]
Message-ID: <a684f28033020f45021de3ef40a1599e78fececf.camel@t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
The attached patch fixes PR 111001.
Committed to master, cherry-picked to GCC-13, GCC-12 and GCC-11.
Sanity tested with 'make all-gcc'.
Bootstrapped on GCC-13 sh4-linux by Adrian.
Cheers,
Oleg
gcc/ChangeLog:
PR target/111001
* config/sh/sh_treg_combine.cc (sh_treg_combine::record_set_of_reg):
Skip over nop move insns.
[-- Attachment #2: 0001-SH-Fix-PR-111001.patch --]
[-- Type: text/x-patch, Size: 1258 bytes --]
From 4414818f4e5de54ea3c353e2ebb2e79a89ae211b Mon Sep 17 00:00:00 2001
From: Oleg Endo <olegendo@gcc.gnu.org>
Date: Mon, 23 Oct 2023 22:08:37 +0900
Subject: [PATCH] SH: Fix PR 111001
gcc/ChangeLog:
PR target/111001
* config/sh/sh_treg_combine.cc (sh_treg_combine::record_set_of_reg):
Skip over nop move insns.
---
gcc/config/sh/sh_treg_combine.cc | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/gcc/config/sh/sh_treg_combine.cc b/gcc/config/sh/sh_treg_combine.cc
index f6553c0..685ca54 100644
--- a/gcc/config/sh/sh_treg_combine.cc
+++ b/gcc/config/sh/sh_treg_combine.cc
@@ -731,9 +731,16 @@ sh_treg_combine::record_set_of_reg (rtx reg, rtx_insn *start_insn,
new_entry.cstore_type = cstore_inverted;
}
else if (REG_P (new_entry.cstore.set_src ()))
{
- // If it's a reg-reg copy follow the copied reg.
+ // If it's a reg-reg copy follow the copied reg, but ignore
+ // nop copies of the reg onto itself.
+ if (REGNO (new_entry.cstore.set_src ()) == REGNO (reg))
+ {
+ i = prev_nonnote_nondebug_insn_bb (i);
+ continue;
+ }
+
new_entry.cstore_reg_reg_copies.push_back (new_entry.cstore);
reg = new_entry.cstore.set_src ();
i = new_entry.cstore.insn;
--
libgit2 1.3.2
reply other threads:[~2023-10-23 13:28 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=a684f28033020f45021de3ef40a1599e78fececf.camel@t-online.de \
--to=oleg.endo@t-online.de \
--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).