public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: [Ping] [C++ Patch] PR 60373
Date: Tue, 20 May 2014 13:27:00 -0000	[thread overview]
Message-ID: <537B5793.4070207@oracle.com> (raw)
In-Reply-To: <53716519.8010802@oracle.com>

Hi,

On 05/13/2014 02:19 AM, Paolo Carlini wrote:
> Hi,
>
> in this issue Marc noticed that the warning for ignored attribute 
> visibility is truncated when the previous declaration belongs to a 
> system header. Luckily the problem can be neatly fixed because it's 
> just a consequence of not using warning_at + inform, as we should 
> anyway. The other hunk in the patch tweaks the only other remaining 
> warning_at pair I found in the file, should be a rather benign one, 
> but better adjusting it too.
>
> Tested x86_64-linux.
Ping rather early because this one should be rather straightforward...

Thanks!
Paolo.

  reply	other threads:[~2014-05-20 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  0:21 Paolo Carlini
2014-05-20 13:27 ` Paolo Carlini [this message]
2014-05-20 14:08 ` 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=537B5793.4070207@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@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).