From: edmar <edmar@freescale.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA] [PR44618] [PowerPC] Wrong code for -frename-registers
Date: Fri, 20 May 2011 09:13:00 -0000 [thread overview]
Message-ID: <4DD59554.9040806@freescale.com> (raw)
In-Reply-To: <BANLkTim9R5g=VQ-ZPnThi7sAyQqn10=xcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
This time I put them in a tar file, to make sure the mail client don't
mess with them.
(ChangeLog is already inside the patch as well)
After I complete the regression tests, I will post a new version against
latest
subversion revision. Will post it here and on bugzilla.
Thanks,
Edmar
On 05/19/2011 04:36 PM, David Edelsohn wrote:
> 010-06-21 Edmar Wienskoski edmar@freescale.com
>
> * rs6000.md (save_gpregs_<mode>): Replaced pattern with a set
> of similar patterns, where the MATCH_OPERAND for the function
> argument is replaced with individual references to hardware
> registers.
> * rs6000.md (save_fpregs_<mode>): Ditto
> * rs6000.md (save_gpregs_<mode>): Ditto
> * rs6000.md (restore_gpregs_<mode>): Ditto
> * rs6000.md (return_and_restore_gpregs_<mode>): Ditto
> * rs6000.md (return_and_restore_fpregs_<mode>): Ditto
> * rs6000.md (return_and_restore_fpregs_aix_<mode>): Ditto
>
> Okay.
>
> Did you intend to include the gcc44 diff?
>
> Also, it's better if you include the ChangeLog inline and the patch as
> an attachment, instead of vice versa.
>
> Thanks, David
>
> .
>
[-- Attachment #2: sub_ppc_rnreg3.tar --]
[-- Type: application/x-tar, Size: 20480 bytes --]
next prev parent reply other threads:[~2011-05-19 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 8:31 David Edelsohn
2011-05-20 9:13 ` edmar [this message]
2011-05-24 4:46 ` edmar
2011-05-25 15:11 ` David Edelsohn
2011-06-13 17:27 ` edmar
-- strict thread matches above, loose matches on Subject: below --
2011-05-19 18:10 edmar
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=4DD59554.9040806@freescale.com \
--to=edmar@freescale.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).