This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++ preview patch] PR 44277
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 31 Oct 2011 17:51:48 +0100
- Subject: Re: [C++ preview patch] PR 44277
- References: <4EAD9AE8.7070703@oracle.com> <4EAEB18C.7000306@redhat.com>
Hi,
How does it work to warn in convert_like_real instead?
the problem is that (expr, totype) can be a lot of different things for
which we want to warn, can be a zero and a pointer for assignments, but,
when totype is a BOOLEAN_TYPE expr can be an EQ_EXPR or NEQ_EXPR and
then the operands various things depending on whether we are looking for
pointer, data member pointer, etc, on the left or on the right of the ==
or != sign. In other terms, the pattern matching doesn't seem matter of
a few lines. I'm annoyed by this. Also, for the assignment case, I'm
getting duplicate warnings, maybe can be fixed.
Do you think there is no neat way to implement my idea of avoiding
generating those implicit 0s in the first place? The internals of the
front-end, seem very c++98-ish for null pointers ;)
Paolo.