public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vadmium+gc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30006] Compound literal in structure initializer causes missing initializer warning to happen
Date: Wed, 18 Apr 2012 12:25:00 -0000	[thread overview]
Message-ID: <bug-30006-4-d3DawbLmVe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-30006-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30006

Marty <vadmium+gc at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vadmium+gc at gmail dot com

--- Comment #3 from Marty <vadmium+gc at gmail dot com> 2012-04-18 12:22:48 UTC ---
Possibly related: Bug 36446, Bug 47772

Here’s an example where the warning is completely false. There are no missing
initialisers because I’ve listed them both.

struct {
    struct {
        int first;
        int second;
    } inner;
} outer = {
    .inner.first = 1,
    /* Warning -> */ .inner.second = 2,
};

With the -Wextra flag, GCC 4.7.0 produced:

bug.c:8:22: warning: missing initializer [-Wmissing-field-initializers]
bug.c:8:22: warning: (near initialization for ‘outer.inner.second’)
[-Wmissing-field-initializers]


       reply	other threads:[~2012-04-18 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-30006-4@http.gcc.gnu.org/bugzilla/>
2012-04-18 12:25 ` vadmium+gc at gmail dot com [this message]
2012-04-18 14:00 ` manu at gcc dot gnu.org
2006-11-28  8:47 [Bug c/30006] New: Compound literal in structure initializer causes irrelevant warning yar at bsd dot chem dot msu dot ru
2006-12-02  8:10 ` [Bug c/30006] Compound literal in structure initializer causes missing initializer warning to happen pinskia at gcc dot gnu dot org
2008-06-06  9:51 ` he at uninett dot no

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-30006-4-d3DawbLmVe@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: link
Be 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).