http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
Paolo Carlini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
--- Comment #6 from paolo at gcc dot gnu.org
2011-11-01 23:28:23 UTC ---
Author: paolo
Date: Tue Nov 1 23:28:19 2011
New Revision: 180750
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180750
Log:
/cp
2011-11-01 Paolo Carlini
PR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
--- Comment #5 from Paolo Carlini 2011-10-17
23:29:00 UTC ---
Humm, I already see something wrong in my wild idea: the patchlet triggers also
in conditionals, eg 'if (!p)'...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
--- Comment #4 from Paolo Carlini 2011-10-17
23:12:58 UTC ---
Jason, would it make sense to produce the warning in cp_convert_to_pointer? I
see the function does *not* have a complain argument (which would be used in
the existing error calls), an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
--- Comment #2 from Jason Merrill 2011-10-17
18:53:07 UTC ---
That seems reasonable, though I wouldn't have it enabled by default or -Wall.
Could start with replacing convert_and_check with a cp_convert_and_check that
also performs this check.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44277
Paolo Carlini changed:
What|Removed |Added
CC|gcc-bugs at gcc dot gnu.org |jason at gcc dot gnu.org
--- Comment #1 f
