From: Renlin Li <renlin.li@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Ramana.Radhakrishnan@arm.com,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
law@redhat.com
Subject: Re: [PING][PATCH][4.9]Backport "Fix register corruption bug in ree"
Date: Thu, 16 Apr 2015 09:32:00 -0000 [thread overview]
Message-ID: <552F81BF.9020800@arm.com> (raw)
In-Reply-To: <1C23526A7C42DB45BBF55B662C7C530E430D20FFFD@BUNGLE.Emea.Arm.com>
Ping~
Regards,
Renlin Li
On 16/04/15 10:09, wrote:
> Ping~
> Anybody has time to review it?
>
>
> Regards,
> Renlin Li
>
> On 06/02/15 17:48, Renlin Li wrote:
>> Hi all,
>>
>> This is a backport patch for branch 4.9. You can find the original=20
>> patch here:https://gcc.gnu.org/ml/gcc-patches/2014-09/msg00356.html
>> And it has been commit on the trunk as r215205.
>>
>> This fixes a few libstdc++-v3 test suite failures.
>> x86_64 bootstraps Okay, aarch64_be-none-elf libstdc++-v3 tested Okay.
>>
>> Okay to commit on branch 4.9?
>>
>> Regards,
>> Renlin Li
>>
>> 2015-02-06 Renlin Li<renlin.li@arm.com>
>>
>> Backport from mainline
>> 2014-09-12 Wilco Dijkstra<wilco.dijkstra@arm.com>
>>
>> * gcc/ree.c (combine_reaching_defs): Ensure inserted copy don't=20
>> change
>> the number of hard registers.
>>
next parent reply other threads:[~2015-04-16 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1C23526A7C42DB45BBF55B662C7C530E430D20FFFD@BUNGLE.Emea.Arm.com>
2015-04-16 9:32 ` Renlin Li [this message]
2015-04-28 16:21 ` Renlin Li
2015-06-04 13:20 ` Renlin Li
2015-10-29 15:41 ` Ramana Radhakrishnan
2015-10-29 16:41 ` Richard Biener
2015-11-06 17:25 ` Renlin Li
2015-11-09 8:32 ` Richard Biener
2015-02-06 17:48 [PATCH][4.9]Backport " Renlin Li
2015-03-02 14:14 ` [PING][PATCH][4.9]Backport " Renlin Li
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=552F81BF.9020800@arm.com \
--to=renlin.li@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).