http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53521
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.3/4.4/4.5/4.6/4.7/4.8 |[4.5/4.6/4.7/4.8
|Regression] Zero-byte |Regression] Zero-byte
|memory leak with zero-sized |memory leak with zero-sized
|array constructor |array constructor
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-30
09:54:31 UTC ---
Well, I think this is a valgrind issue and not a real "leak". Whether you
want to "optimize" code for the non-NULL case by omitting the NULL check is
another question of course. It's definitely not wrong-code IMHO.
