public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5939: Segfault for array initialization
Date: Wed, 13 Mar 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020313182602.6706.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/5939; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: kroening@turing.modck.cs.cmu.edu
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/5939: Segfault for array initialization
Date: Wed, 13 Mar 2002 13:18:25 -0500

 This has been fixed for at least 3.0.4.
 
 Thanks,
 Andrew Pinski
 
 
 On Wednesday, March 13, 2002, at 12:55 ,=20
 kroening@turing.modck.cs.cmu.edu wrote:
 
 > System: Linux turing.modck.cs.cmu.edu 2.4.17 #1 SMP-BIGMEM+SMP-001 Thu=20=
 
 > Jan 31 05:34:15 EST 2002 i686 unknown
 > Architecture: i686
 > host: i686-pc-linux-gnu
 > build: i686-pc-linux-gnu
 > target: i686-pc-linux-gnu
 > configured with: ../gcc-3.0.1/configure=20
 > --prefix=3D/usr/local/libexec/gcc-3.0.1
 >> Description:
 > Segmentation fault
 >
 > test.c: In function `main':
 > test.c:5: warning: excess elements in array initializer
 > test.c:5: warning: (near initialization for =01')
 > test.c:5: Internal error: Segmentation fault
 > Please submit a full bug report,
 > with preprocessed source if appropriate.
 > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 >
 >> How-To-Repeat:
 > gcc test.c -o test
 >
 > test.c:
 >
 > int main()
 >  {
 >   int a[0]=3D{ 0 };
 >  }
 


             reply	other threads:[~2002-03-13 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 10:26 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25 17:25 rth
2002-03-13 10:06 kroening

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=20020313182602.6706.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).