http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54202
--- Comment #2 from Thiago Macieira <thiago at kde dot org> 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 this warning can't be improved to be certain, I'd recommend at least changing the text, like the -Wuninitialized one: 'varname' may be used uninitialized in this function When GCC warnings are assertive, like the "will break strict aliasing" one, we go an extra mile to try and fix them.
