From: Vladimir Makarov <vmakarov@redhat.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Patch to fix PR92283
Date: Fri, 29 Nov 2019 23:23:00 -0000 [thread overview]
Message-ID: <4ff6c9c9-e8a7-92f8-4eed-d01465004019@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92283
The patch has no test because it is very hard to reproduce PR and check
the patch even on a specific GCC revision.
The patch was successfully bootstrapped and tested on x86-64.
Committed as r278865
[-- Attachment #2: pr92283.patch --]
[-- Type: text/x-patch, Size: 1360 bytes --]
Index: ChangeLog
===================================================================
--- ChangeLog (revision 278864)
+++ ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2019-11-29 Vladimir Makarov <vmakarov@redhat.com>
+
+ PR rtl-optimization/92283
+ * lra.c (lra): Update reg notes after inheritance sub-pass and
+ before constraint sub-pass.
+
2019-11-29 Richard Biener <rguenther@suse.de>
PR tree-optimization/91003
Index: lra.c
===================================================================
--- lra.c (revision 278864)
+++ lra.c (working copy)
@@ -2473,7 +2473,7 @@ lra (FILE *f)
But don't remove dead insns or change global live
info as we can undo inheritance transformations after
inheritance pseudo assigning. */
- lra_create_live_ranges (true, false);
+ lra_create_live_ranges (true, !lra_simple_p);
live_p = true;
/* If we don't spill non-reload and non-inheritance
pseudos, there is no sense to run memory-memory move
@@ -2514,6 +2514,11 @@ lra (FILE *f)
}
}
while (fails_p);
+ if (! live_p) {
+ /* We need the correct reg notes for work of constraint sub-pass. */
+ lra_create_live_ranges (true, true);
+ live_p = true;
+ }
}
/* Don't clear optional reloads bitmap until all constraints are
satisfied as we need to differ them from regular reloads. */
reply other threads:[~2019-11-29 22:11 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=4ff6c9c9-e8a7-92f8-4eed-d01465004019@redhat.com \
--to=vmakarov@redhat.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).