public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43167] Warnings should not be disabled when instantiating templates defined in system headers
Date: Thu, 25 Feb 2010 00:17:00 -0000 [thread overview]
Message-ID: <20100225001702.14434.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43167-1313@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from ian at airs dot com 2010-02-25 00:17 -------
Paolo: It is definitely a complicated case, the concern about false positives
is entirely valid. This leads us to introducing more command line options,
plus getting #pragma GCC diagnostic to work. I'm not sure what the best
solution is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43167
next prev parent reply other threads:[~2010-02-25 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 19:34 [Bug c++/43167] New: " ian at airs dot com
2010-02-24 19:35 ` [Bug c++/43167] " pinskia at gcc dot gnu dot org
2010-02-24 19:37 ` pinskia at gcc dot gnu dot org
2010-02-24 19:39 ` pinskia at gcc dot gnu dot org
2010-02-24 19:42 ` pinskia at gcc dot gnu dot org
2010-02-24 20:56 ` ian at airs dot com
2010-02-24 21:43 ` paolo dot carlini at oracle dot com
2010-02-24 22:33 ` ian at airs dot com
2010-02-24 22:47 ` paolo dot carlini at oracle dot com
2010-02-24 22:52 ` manu at gcc dot gnu dot org
2010-02-24 22:56 ` pinskia at gcc dot gnu dot org
2010-02-24 23:00 ` pinskia at gcc dot gnu dot org
2010-02-24 23:20 ` manu at gcc dot gnu dot org
2010-02-25 0:17 ` ian at airs dot com [this message]
2010-04-21 19:02 ` redi at gcc dot gnu dot org
[not found] <bug-43167-4@http.gcc.gnu.org/bugzilla/>
2020-06-19 19:10 ` redi at gcc dot gnu.org
2024-03-05 14:29 ` redi 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=20100225001702.14434.qmail@sourceware.org \
--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).