From: Vladimir Makarov <vmakarov@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: patch to fix PR57468
Date: Thu, 06 Jun 2013 21:19:00 -0000 [thread overview]
Message-ID: <51B0F9CD.5070109@redhat.com> (raw)
The following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57468
The patch actually restore the LRA behaviour for x86/x86-64 before rev.
199298. The revision was added for PPC SDmode value correct
generation. So it is really needed for PPC64 and badly hurts x86/x86-64
performance (by doing secondary memory reloads when one pseudo is spilled).
The patch was successfully bootstrapped and tested on x86/x86-64 (with
patch for pr57459).
Although the change in i386.c, it only concerns to LRA. So I've
decided to commit it without x86/x86-64 maintainer approval. May be I
am wrong in this situation. If somebody objects I am ready to revert
the patch and wait for an approval.
Committed as rev. 199764.
2013-06-06 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/57468
* config/i386/i386.c (inline_secondary_memory_needed): Ignore
spilled pseudos.
next reply other threads:[~2013-06-06 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 21:19 Vladimir Makarov [this message]
2013-06-07 1:23 David Edelsohn
2013-06-07 14:29 ` 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=51B0F9CD.5070109@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).