This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: -Wmissing-field-initializers got shot in the leg
- From: Georg GCC User <georggcc at googlemail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Tue, 3 Jan 2017 12:34:24 +0100
- Subject: Re: -Wmissing-field-initializers got shot in the leg
- Authentication-results: sourceware.org; auth=none
- References: <CAJqixVHd5p0oDMXDxW1EK8fSFQ+14+XsrfOYrJUcirjvS0D-Vg@mail.gmail.com> <CAH6eHdSr6gNRXK3f=qR6Q13oOKTu3RySk_GFr5R7e_vkAPxdFg@mail.gmail.com>
On Fri, Dec 30, 2016 at 2:15 PM, Jonathan Wakely <jwakely.gcc@gmail.com> 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.