public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "smeuuh at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36489]  New: Warning "initialized field overwritten" wrongly triggers with multidimensional arrays
Date: Tue, 10 Jun 2008 16:26:00 -0000	[thread overview]
Message-ID: <bug-36489-16304@http.gcc.gnu.org/bugzilla/> (raw)

Hi,
This code :
int t[10][10] = {
                [1][2] = 1,
                [1][3] = 2
        };
warns with "initialized field overwritten" under -Wextra with gcc 4.3.0,
although it's perfectly valid.
Antoine Levitt


-- 
           Summary: Warning "initialized field overwritten" wrongly triggers
                    with multidimensional arrays
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: smeuuh at gmail dot com
 GCC build triplet: i386-pc-linux
  GCC host triplet: i386-pc-linux
GCC target triplet: i386-pc-linux


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


             reply	other threads:[~2008-06-10 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 16:26 smeuuh at gmail dot com [this message]
2008-12-28  1:21 ` [Bug c/36489] [4.3/4.4 Regression] " pinskia at gcc dot gnu dot org
2008-12-29 16:42 ` jakub at gcc dot gnu dot org
2008-12-29 21:51 ` rguenth at gcc dot gnu dot org
2009-01-01 19:42 ` jakub at gcc dot gnu dot org
2009-01-01 19:46 ` [Bug c/36489] [4.3 " jakub at gcc dot gnu dot org
2009-01-24 10:25 ` rguenth at gcc dot gnu dot org
2009-08-04 12:41 ` rguenth at gcc dot gnu dot org
2010-05-22 18:31 ` rguenth at gcc dot gnu dot 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-36489-16304@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).