public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35669] NULL (__null) not considered different from 0 with C++
Date: Tue, 16 Feb 2010 18:43:00 -0000 [thread overview]
Message-ID: <20100216184348.28983.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35669-14453@http.gcc.gnu.org/bugzilla/>
------- Comment #25 from jason at redhat dot com 2010-02-16 18:43 -------
Subject: Re: NULL (__null) not considered different from 0
with C++
On 02/16/2010 01:27 PM, manu at gcc dot gnu dot org wrote:
> I guess you mean Wconversion-null instead of Wconversion-nul. Fine.
OK with that change.
> Any suggestions to give better location information in this warning? I guess
> the location of null_node is useless.
No real suggestions; to avoid using input_location we'd need to track
locations all the way through the overload resolution code.
I wonder if in 4.6 we want to start wrapping uses of shared nodes such
as null_node or decls in order to retain location information.
Jason
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35669
next prev parent reply other threads:[~2010-02-16 18:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 20:06 [Bug c++/35669] New: " l dot lunak at suse dot cz
2008-03-22 21:11 ` [Bug c++/35669] " rguenth at gcc dot gnu dot org
2008-03-22 23:16 ` l dot lunak at suse dot cz
2008-03-23 14:08 ` manu at gcc dot gnu dot org
2008-03-23 19:00 ` truedfx at gentoo dot org
2008-03-23 19:44 ` manu at gcc dot gnu dot org
2008-03-23 20:16 ` l dot lunak at suse dot cz
2008-03-23 22:18 ` manu at gcc dot gnu dot org
2009-02-12 17:57 ` peter at cordes dot ca
2009-04-28 20:01 ` mdorey at bluearc dot com
2009-04-29 12:51 ` bangerth at gmail dot com
2009-04-29 13:22 ` l dot lunak at suse dot cz
2009-04-29 16:47 ` mdorey at bluearc dot com
2009-12-08 10:49 ` redi at gcc dot gnu dot org
2009-12-21 20:02 ` mdorey at bluearc dot com
2009-12-22 10:36 ` jwakely dot gcc at gmail dot com
2009-12-22 18:12 ` mdorey at bluearc dot com
2010-02-14 20:19 ` manu at gcc dot gnu dot org
2010-02-14 21:47 ` l dot lunak at suse dot cz
2010-02-14 22:06 ` manu at gcc dot gnu dot org
2010-02-16 17:11 ` jason at gcc dot gnu dot org
2010-02-16 18:02 ` echristo at apple dot com
2010-02-16 18:06 ` manu at gcc dot gnu dot org
2010-02-16 18:09 ` echristo at apple dot com
2010-02-16 18:27 ` manu at gcc dot gnu dot org
2010-02-16 18:43 ` jason at redhat dot com [this message]
2010-02-20 21:32 ` manu at gcc dot gnu dot org
2010-02-20 21:38 ` manu at gcc dot gnu dot org
2010-02-20 23:51 ` jason at gcc dot gnu dot 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=20100216184348.28983.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).