https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #6 from Thiago Macieira ---
ping.
If you can't fix GCC so that it can prove that the free is on a non-heap
object, then please change the warning to indicate that GCC may be wrong. For
example:
warning: free() may be called with non
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #5 from Andrew Pinski 2012-08-08
19:00:58 UTC ---
Even the printf format warnings are this way too
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #4 from Thiago Macieira 2012-08-08 14:53:13
UTC ---
(In reply to comment #3)
> Note that even for the uninitialized use case we warn for functions
> that may be never executed at runtime. So - are you happy with the
> definitive warn
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #3 from Richard Guenther 2012-08-08
14:36:03 UTC ---
(In reply to comment #2)
> To be honest, I don't want false-positive warnings. The code and data are
> constructed so that it never frees the non-heap object (it has a reference
> c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #2 from Thiago Macieira 2012-08-08 14:21:59
UTC ---
To be honest, I don't want false-positive warnings. The code and data are
constructed so that it never frees the non-heap object (it has a reference
count of -1). If the driver to th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
