On Fri, Dec 30, 2016 at 2:15 PM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: > On 30 December 2016 at 09:26, Georg GCC User wrote: > No, it's nothing to do with that. The behaviour you've observed with > designated initializers has been how it works since the warning option > was first added back in 2004, see https://gcc.gnu.org/r85638 >> Is there some other way to make GCC warn, or will a change request >> be in order? > > I think so, since the current behaviour is documented and intentional. It seems like the change had been requested in 2009. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39589 I have added my thoughts.
