public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Shujing Zhao <pearly.zhao@oracle.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       Paolo Carlini <paolo.carlini@oracle.com>
Subject: Re: [PATCH C/C++] Fix some diagnostics problems
Date: Tue, 08 Jun 2010 04:09:00 -0000	[thread overview]
Message-ID: <4C0DC20D.7020201@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1006071326510.16740@digraph.polyomino.org.uk>

On 06/07/2010 09:27 PM, Joseph S. Myers wrote:
> On Mon, 7 Jun 2010, Shujing Zhao wrote:
> 
>> Ok. Since there is no obvious requirement to change them, I only take out the
>> part that fixes the existing 18n problems.
>> The following is the patch for C frontend.
> 
> The patch you attached - which was for fold-const.c and tree-inline.c, not 
> the C front end - is OK if it passed bootstrap with no regressions.
> 
Bootstrap with no regressions. Committed trunk at revision 160419.

Thanks
Pearly

  reply	other threads:[~2010-06-08  4:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  9:39 Shujing Zhao
2010-06-05 13:18 ` Joseph S. Myers
2010-06-07  9:33   ` Shujing Zhao
2010-06-07 13:27     ` Joseph S. Myers
2010-06-08  4:09       ` Shujing Zhao [this message]
2010-06-08  4:13 Shujing Zhao
2010-06-08 10:42 ` Joseph S. Myers
2010-06-08 13:45   ` Gabriel Dos Reis
2010-06-08 19:08 ` Jason Merrill
2010-06-08 19:11   ` Jason Merrill
2010-06-09  3:20   ` Shujing Zhao
2010-06-09  4:39     ` Jason Merrill
2010-06-09  9:23   ` Shujing Zhao
2010-06-09 13:00     ` Jason Merrill
2010-06-10  7:07       ` Shujing Zhao
2010-06-10 13:13         ` Jason Merrill
2010-06-11  6:02           ` Shujing Zhao
2010-06-11  9:33             ` Manuel López-Ibáñez
2010-06-11  9:40       ` Manuel López-Ibáñez
2010-06-11 10:50         ` Shujing Zhao
2010-06-11 11:22           ` Manuel López-Ibáñez
2010-06-12  7:55             ` Shujing Zhao
2010-06-12 13:44               ` Jason Merrill

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=4C0DC20D.7020201@oracle.com \
    --to=pearly.zhao@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=paolo.carlini@oracle.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).