From: Vladimir Makarov <vmakarov@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: patch to fix PR57468
Date: Fri, 07 Jun 2013 14:29:00 -0000 [thread overview]
Message-ID: <51B1EE59.20004@redhat.com> (raw)
In-Reply-To: <CAGWvny=YOxk45SdLEr0YZX6MWMtK=4j-uW1g=+TCverP2N6afQ@mail.gmail.com>
On 13-06-06 9:22 PM, David Edelsohn wrote:
>> 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).
> Should the solution for PPC64 be further limited, even on
> PPC64? Is this going to hurt more normal spilling code on PPC64 that
> does not have the strange restrictions of SDmode?
>
>
No, it does not hurt ppc performance. In ppc case, it works the same
way as reload does (and only for SDmode values). I also found LRA
generates a better code for SDmode than reload. I did not figure out
why reload pass uses secondary memory when one pseudo is spilled for ppc
and does not use this for x86/x86-64 although both targets report
necessity of secondary memory in case when one pseudo is spilled. It
requires a lot of time but I should probably still do this.
I hope that Mike checks performance of LRA as I have no hardware to
do this. If he finds any performance degradation, I look at it.
next prev parent reply other threads:[~2013-06-07 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 1:23 David Edelsohn
2013-06-07 14:29 ` Vladimir Makarov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 21:19 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=51B1EE59.20004@redhat.com \
--to=vmakarov@redhat.com \
--cc=dje.gcc@gmail.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).