https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95379
--- Comment #14 from Luc Van Oostenryck <luc.vanoostenryck at gmail dot com> ---
(In reply to Tom Tromey from comment #7)
> The feature was added specifically to mimic what sparse does.
> If sparse changes, I think changing gcc would be appropriate.
Sparse warnings issued when using '{ 0 }' and not '{ }' were not really
intentional, but simply a consequence of how 'usual' initializers are
processed.
I think that '{ 0 }' and '{ }' should behave the same, they're just 2 way to
write the universal zero initializer, and thus there is no reasons to issue
theses warnings with '{ 0 }'.
I've now changed Sparse's default so that these warnings are not issued
anymore.
-- Luc
