public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/5939: Segfault for array initialization
@ 2002-04-25 17:25 rth
  0 siblings, 0 replies; 3+ messages in thread
From: rth @ 2002-04-25 17:25 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, kroening, kroening, nobody

Synopsis: Segfault for array initialization

State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Thu Apr 25 17:25:11 2002
State-Changed-Why:
    Fixed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5939


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c/5939: Segfault for array initialization
@ 2002-03-13 10:26 Andrew Pinski
  0 siblings, 0 replies; 3+ messages in thread
From: Andrew Pinski @ 2002-03-13 10:26 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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 };
 >  }
 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c/5939: Segfault for array initialization
@ 2002-03-13 10:06 kroening
  0 siblings, 0 replies; 3+ messages in thread
From: kroening @ 2002-03-13 10:06 UTC (permalink / raw)
  To: gcc-gnats


>Number:         5939
>Category:       c
>Synopsis:       Segfault for array initialization
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 13 10:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Daniel Kroening
>Release:        3.0.1
>Organization:
Carnegie Mellon University
>Environment:
System: Linux turing.modck.cs.cmu.edu 2.4.17 #1 SMP-BIGMEM+SMP-001 Thu 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 --prefix=/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 \x01')
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]={ 0 };
 }
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-04-26  0:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-25 17:25 c/5939: Segfault for array initialization rth
  -- strict thread matches above, loose matches on Subject: below --
2002-03-13 10:26 Andrew Pinski
2002-03-13 10:06 kroening

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).