public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "webmaster@sky-siteweb.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47772] warnings from -Wmissing-field-initializers contradict documentation Date: Mon, 21 Feb 2011 17:03:00 -0000 [thread overview] Message-ID: <bug-47772-4-vJutTXkc1y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47772-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47772 Jonathan 'Sky' Squirawski <webmaster@sky-siteweb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |webmaster@sky-siteweb.com --- Comment #2 from Jonathan 'Sky' Squirawski <webmaster@sky-siteweb.com> 2011-02-21 16:55:39 UTC --- I've the same problem with gcc 4.5.2. Here another test case: /*==================================*/ typedef struct bar_t { int a; int b; } bar_t; typedef struct foo_ok_t { int bar; bar_t foo; } foo_ok_t; typedef struct foo_nok_t { bar_t bar; bar_t foo; } foo_nok_t; int main(void) { foo_ok_t foo_ok; foo_nok_t foo_nok; foo_ok = (foo_ok_t){ .bar = 32, }; foo_nok = (foo_nok_t){ .bar = (bar_t){ .a = 32, .b = 42 }, }; return 0; } /*==================================*/ The first assignment doesn't trigger any warning, but the second one gives: test.c:29:5: warning: missing initializer test.c:29:5: warning: (near initialization for ‘(anonymous).foo’)
next prev parent reply other threads:[~2011-02-21 16:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-16 20:49 [Bug c/47772] New: " darren at kulp dot ch 2011-02-16 21:08 ` [Bug c/47772] " darren at kulp dot ch 2011-02-21 17:03 ` webmaster@sky-siteweb.com [this message] 2012-04-18 13:00 ` vadmium+gc at gmail dot com 2012-04-18 13:27 ` manu at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-47772-4-vJutTXkc1y@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).