From: Richard Guenther <richard.guenther@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: amodra@gmail.com, Olivier Hainque <hainque@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RS6000] Stack tie fix.
Date: Thu, 12 Apr 2012 16:03:00 -0000 [thread overview]
Message-ID: <CAFiYyc0uupCmOsYwuYkxRAxULC5WyGqbyh5ZCwFYjGqF9HNyDA@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnynzhH907oYC5NV-vnABjPdgrBGJyFM=e-F_Hpoc7FL1jw@mail.gmail.com>
On Thu, Apr 12, 2012 at 5:34 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> On Thu, Apr 12, 2012 at 9:22 AM, Alan Modra <amodra@gmail.com> wrote:
>
>> I tried that. It doesn't work without something else in the insn to
>> stop rtl-dce deleting it, so you may as well use SETs. But thanks for
>> the prod in the right direction. We do get slightly better results
>> when the regs are not hidden away in an UNSPEC, for instance
>> non-stack writes/reads are seen by the alias oracle to not conflict
>> with the epilogue frame deallocation.
>>
>> Bootstrapped etc. powerpc-linux. OK to apply, David?
>>
>> PR target/52828
>> * config/rs6000/rs6000.c (rs6000_emit_stack_tie): Rewrite with
>> tie regs on destination of sets. Delete forward declaration.
>> (rs6000_emit_stack_reset): Update rs6000_emit_stack_tie calls.
>> (rs6000_emit_prologue): Likewise.
>> (rs6000_emit_epilogue): Likewise. Use in place of gen_frame_tie
>> and gen_stack_tie.
>> (is_mem_ref): Use tie_operand to recognise stack ties.
>> * config/rs6000/predicates.md (tie_operand): New.
>> * config/rs6000/rs6000.md (UNSPEC_TIE): Delete.
>> (restore_stack_block): Generate new stack tie rtl.
>> (restore_stack_nonlocal): Likewise.
>> (stack_tie): Update.
>> (frame_tie): Delete.
>
> This probably is getting close to the best we can do with GCC's RTL
> alias analysis infrastructure.
>
> This version is okay, but I also want to give Richi and Olivier an
> opportunity to comment if they still have any concerns.
It looks fine to me.
Richard.
> Thanks, David
next prev parent reply other threads:[~2012-04-12 16:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 8:40 Alan Modra
2012-04-03 14:35 ` Olivier Hainque
2012-04-03 14:56 ` Olivier Hainque
2012-04-03 17:05 ` David Edelsohn
2012-04-04 1:22 ` Alan Modra
2012-04-05 10:36 ` Olivier Hainque
2012-04-05 14:03 ` Alan Modra
2012-04-05 17:23 ` Olivier Hainque
2012-04-06 0:33 ` Alan Modra
2012-04-06 15:25 ` Olivier Hainque
2012-04-11 4:16 ` Alan Modra
2012-04-11 9:00 ` Richard Guenther
2012-04-12 13:23 ` Alan Modra
2012-04-12 15:34 ` David Edelsohn
2012-04-12 16:03 ` Richard Guenther [this message]
2012-04-12 16:08 ` Olivier Hainque
2012-04-12 17:18 ` Olivier Hainque
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=CAFiYyc0uupCmOsYwuYkxRAxULC5WyGqbyh5ZCwFYjGqF9HNyDA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
/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).