public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rjarrett at mathworks dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48914] #pragma GCC diagnostic ignored "-Wc++0x-compat" doesn't work
Date: Tue, 01 Jan 2013 18:05:00 -0000 [thread overview]
Message-ID: <bug-48914-4-4BQ4HLMruv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48914-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48914
Roger Jarrett <rjarrett at mathworks dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rjarrett at mathworks dot
| |com
--- Comment #6 from Roger Jarrett <rjarrett at mathworks dot com> 2013-01-01 18:04:49 UTC ---
Confirmed present in GCC 4.7.1
g++ foo.cpp -Wall -std=c++98
our use case is that we have a code base in transition to C++0x and have
created our own nullptr_t for the platform that have not yet transitioned to
C++0x we would like to acknowledge/suppress this warning in the file that
implements the nullptr_t without resorting to -Wno-c++0x-compat on the commmand
line.
--Roger
next prev parent reply other threads:[~2013-01-01 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 9:40 [Bug middle-end/48914] New: " bero at arklinux dot org
2011-07-24 20:13 ` [Bug c++/48914] " pinskia at gcc dot gnu.org
2011-09-28 17:57 ` paolo.carlini at oracle dot com
2011-09-29 15:40 ` paolo.carlini at oracle dot com
2012-08-02 6:41 ` asmwarrior at gmail dot com
2012-08-02 8:28 ` asmwarrior at gmail dot com
2013-01-01 18:05 ` rjarrett at mathworks dot com [this message]
2013-01-02 18:51 ` rjarrett at mathworks dot com
2013-01-04 10:51 ` manu at gcc dot gnu.org
2014-09-05 16:59 ` manu 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-48914-4-4BQ4HLMruv@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).