public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ruboam at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55578] New: Disabling warnings inside macro definition doesn't work
Date: Mon, 03 Dec 2012 18:41:00 -0000 [thread overview]
Message-ID: <bug-55578-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55578
Bug #: 55578
Summary: Disabling warnings inside macro definition doesn't
work
Classification: Unclassified
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ruboam@gmail.com
When compiling following code with just -Wall option I'm getting below
mentioned warning.
#define FF() \
_Pragma("GCC diagnostic push") \
_Pragma("GCC diagnostic ignored \"-Wunused-variable\"") \
{int x;} \
_Pragma("GCC diagnostic pop")
int main()
{
FF();
return 0;
}
In function 'int main()':
warning: unused variable 'x' [-Wunused-variable]
But when I also specify -no-integrated-cpp or -save-temps options the warning
doesn't show up.
It looks like when preprocessor and compiler work in one shop the warning
doesn't get disabled. BTW this happens for any warning not just with
unused-variable one.
GCC version is: 4.6.2
Command line is: gcc <file-name> -Wall
System is: Linux 2.6.18-238.el5 #1 SMP Sun Dec 19 14:22:44 EST 2010 x86_64
x86_64 x86_64 GNU/Linux
next reply other threads:[~2012-12-03 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 18:41 ruboam at gmail dot com [this message]
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
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@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).