public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stan at tomlinson dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/56078] New: causes cc1 to crash
Date: Tue, 22 Jan 2013 17:28:00 -0000	[thread overview]
Message-ID: <bug-56078-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56078
           Summary: causes cc1 to crash
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: stan@tomlinson.com


tested with 4.6.3 and 3.3.2
possibly illegal syntax, but...
---------------------------

#include <stdio.h>

struct Test {
    int number;
    char name[];
};

struct Test T1 = {
    .number = 'q',
    .name = "zabc",
    .name[0] = 'q'
    };

main ()
{
    printf( "%s:%c\n", T1.name, T1.number );
}

--------------------
n.c:11:2: internal compiler error: Segmentation fault
Please submit a full bug report...


             reply	other threads:[~2013-01-22 17:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 17:28 stan at tomlinson dot com [this message]
2013-01-22 22:37 ` [Bug c/56078] " pinskia at gcc dot gnu.org
2013-01-23  7:30 ` mpolacek at gcc dot gnu.org
2013-01-23  8:07 ` jakub at gcc dot gnu.org
2013-01-23 14:23 ` jakub at gcc dot gnu.org
2013-01-23 14:33 ` jakub at gcc dot gnu.org
2013-01-23 17:53 ` joseph at codesourcery dot com
2013-01-24 13:28 ` jakub at gcc dot gnu.org
2013-01-24 13:33 ` jakub at gcc dot gnu.org
2013-01-24 17:00 ` jakub at gcc dot gnu.org
2013-01-24 17:02 ` jakub at gcc dot gnu.org
2014-03-13 18:16 ` mpolacek 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-56078-4@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).