From: Alexandre Oliva <oliva@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Vladimir Makarov <vmakarov@redhat.com>,
zsojka@seznam.cz, GCC Patches <gcc-patches@gcc.gnu.org>,
wilson@gcc.gnu.org
Subject: Re: [PR103302] skip multi-word pre-move clobber during lra
Date: Wed, 23 Feb 2022 19:39:35 -0300 [thread overview]
Message-ID: <orpmndus0o.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAFiYyc0q5nKKEUmbjD4S0FBgp+Zuvvz=OnVCqVUecAhER9i8Sw@mail.gmail.com> (Richard Biener's message of "Mon, 21 Feb 2022 08:13:32 +0100")
On Feb 21, 2022, Richard Biener <richard.guenther@gmail.com> wrote:
>> Ok to revert commit r12-5852-g50e8b0c9bca6cdc57804f860ec5311b641753fbb
> OK. Please re-open the bug as appropriate.
Thanks. I've reopened it. Here's what I'm installing. I'm not
reverting the testcase, since it stopped failing even before the patch
was put in.
Revert commit r12-5852-g50e8b0c9bca6cdc57804f860ec5311b641753fbb
The patch for PR103302 caused PR104121, and extended the live ranges
of LRA reloads.
for gcc/ChangeLog
PR target/104121
PR target/103302
* expr.cc (emit_move_multi_word): Restore clobbers during LRA.
---
gcc/expr.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/expr.cc b/gcc/expr.cc
index 35e40299753bb..5f7142b975ada 100644
--- a/gcc/expr.cc
+++ b/gcc/expr.cc
@@ -3929,7 +3929,7 @@ emit_move_multi_word (machine_mode mode, rtx x, rtx y)
hard regs shouldn't appear here except as return values.
We never want to emit such a clobber after reload. */
if (x != y
- && ! (lra_in_progress || reload_in_progress || reload_completed)
+ && ! (reload_in_progress || reload_completed)
&& need_clobber != 0)
emit_clobber (x);
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-02-23 22:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 5:37 Alexandre Oliva
2021-12-08 23:12 ` Jeff Law
2021-12-09 2:25 ` Alexandre Oliva
2021-12-09 4:08 ` Alexandre Oliva
2021-12-09 6:03 ` Jeff Law
2021-12-15 8:22 ` Alexandre Oliva
2021-12-15 16:00 ` Jeff Law
2022-02-18 23:27 ` Alexandre Oliva
2022-02-21 7:13 ` Richard Biener
2022-02-23 22:39 ` Alexandre Oliva [this message]
2022-03-01 20:15 ` Alexandre Oliva
2022-03-02 12:25 ` Alexandre Oliva
2022-03-02 14:21 ` Vladimir Makarov
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=orpmndus0o.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=vmakarov@redhat.com \
--cc=wilson@gcc.gnu.org \
--cc=zsojka@seznam.cz \
/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).