public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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: Mon, 13 Jun 2011 17:27:00 -0000	[thread overview]
Message-ID: <4DF62CF2.6040905@freescale.com> (raw)
In-Reply-To: <BANLkTi=83-SObwZqZXJo+upkewig2TUZKQ@mail.gmail.com>

David,

I realized I did not "reply to all" when I first got your email.
You may have my email in your spam filter.

The issue is that I don't have WAA, and as Richard Guenther suggestion,
I want to ask if you could to do the commit for Freescale.

Thanks in advance for your patience.

In reference to: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44618

Regards,
Edmar


On 05/25/2011 09:43 AM, David Edelsohn wrote:
> On Mon, May 23, 2011 at 5:53 PM, edmar<edmar@freescale.com>  wrote:
>> I completed re-testing everything.
>> It turns out I cannot reproduce the original error on gcc-4.4 (rev 173968)
>> So, I am submitting only the patch that I tested for gcc-4.5/4.6/4.7
>>
>> Regression tested for e500mc target on:
>> 4.5: Revision: 173928
>> 4.6: Revision: 173936
>> trunk: Revision: 173966
>>
>> The patch gcc.fix_rnreg4 applies directly to 4.6, 4.7 (1 line offset),
>> and 4.5 (-632 lines offset)
> Are you re-asking for approval?
>
> The patch is okay.
>
> Thanks, David
>
> P.S. Please include the ChangeLog entry inline in the email message
> and attach the patch to the email if it is large.  No tar files.
>
> .
>


  reply	other threads:[~2011-06-13 15:32 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
2011-05-24  4:46 ` edmar
2011-05-25 15:11   ` David Edelsohn
2011-06-13 17:27     ` edmar [this message]
  -- 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=4DF62CF2.6040905@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).