public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55578] Disabling warnings inside macro definition doesn't work
Date: Sun, 09 Dec 2012 00:31:00 -0000 [thread overview]
Message-ID: <bug-55578-4-BoVwRMcKKh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55578-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55578
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-12-09
Ever Confirmed|0 |1
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-09 00:31:40 UTC ---
Confirmed. It only happens with the C++ front-end though. The exact same code
does not warn with the C front-end. I think this might be the pre-ahead of
time tokenizer that happens for the C++ front-end but does not happen for C.
next prev parent reply other threads:[~2012-12-09 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 18:41 [Bug c++/55578] New: " ruboam at gmail dot com
2012-12-05 13:07 ` [Bug c++/55578] " paolo.carlini at oracle dot com
2012-12-09 0:31 ` pinskia at gcc dot gnu.org [this message]
2021-04-26 9:34 ` vz-gcc at zeitlins dot org
2022-10-04 0:37 ` lhyatt at gcc dot gnu.org
2022-10-04 16:04 ` vz-gcc at zeitlins dot org
2022-10-05 22:08 ` lhyatt at gcc dot gnu.org
2022-10-06 1:31 ` vz-gcc at zeitlins dot org
2022-10-06 1:58 ` lhyatt at gcc dot gnu.org
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=bug-55578-4-BoVwRMcKKh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).