public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Terry Guo" <terry.guo@arm.com>
To: "'Paolo Carlini'" <paolo.carlini@oracle.com>
Cc: <gcc-patches@gcc.gnu.org>,	<libstdc++@gcc.gnu.org>,
	<ro@CeBiTec.Uni-Bielefeld.DE>,	<mikestump@comcast.net>,
	"Richard Earnshaw" <Richard.Earnshaw@arm.com>,
	"'Paolo Bonzini'" <bonzini@gnu.org>
Subject: RE: [Ping][PATCH, libstdc++-v3] Enable to cross-test libstdc++ on simulator
Date: Fri, 06 Apr 2012 07:49:00 -0000	[thread overview]
Message-ID: <000601cd13c9$e9c26d80$bd474880$@guo@arm.com> (raw)
In-Reply-To: <4F726600.6090705@oracle.com>

> -----Original Message-----
> From: Paolo Carlini [mailto:paolo.carlini@oracle.com]
> Sent: Wednesday, March 28, 2012 9:15 AM
> To: Terry Guo
> Cc: gcc-patches@gcc.gnu.org; libstdc++@gcc.gnu.org; ro@CeBiTec.Uni-
> Bielefeld.DE; mikestump@comcast.net; Richard Earnshaw; 'Paolo Bonzini'
> Subject: Re: [Ping][PATCH, libstdc++-v3] Enable to cross-test libstdc++
> on simulator
> 
> On 03/28/2012 03:15 AM, Terry Guo wrote:
> > Hello,
> >
> > Thanks Paolo Carlini for pointing out that I should put code changes
> in
> > Makefile.am. This updated patch addresses this issue. Is it OK to
> trunk?
> Sure, thanks.
> 

This patch was committed into trunk at March 28. And I just verified that it
also works for gcc 4.7 branch and 4.6 branch. So can I back port it to 4.7
and 4.6 branch?

BR,
Terry


  reply	other threads:[~2012-04-06  7:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  1:15 Terry Guo
2012-03-28  1:18 ` Paolo Carlini
2012-04-06  7:49   ` Terry Guo [this message]
2012-04-06 13:27     ` Mike Stump
     [not found] <4f56f0ab.c107440a.725e.3322SMTPIN_ADDED@mx.google.com>
2012-03-07  8:56 ` Jonathan Wakely
2012-03-10 23:25 ` Jonathan Wakely
2012-03-12  2:18   ` Terry Guo
2012-03-12 18:52   ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
2012-03-07  5:22 Terry Guo
2012-03-23 12:44 ` Paolo Carlini
2012-03-23 13:03   ` Paolo Bonzini
2012-03-23 13:38     ` Paolo Carlini

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='000601cd13c9$e9c26d80$bd474880$@guo@arm.com' \
    --to=terry.guo@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=paolo.carlini@oracle.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).