public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
@ 2001-12-07 5:56 mwg
0 siblings, 0 replies; 5+ messages in thread
From: mwg @ 2001-12-07 5:56 UTC (permalink / raw)
To: gcc-gnats, debian-gcc
>Number: 5041
>Category: c
>Synopsis: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Fri Dec 07 05:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Wladimir Mutel
>Release: 3.0.2 (Debian) (Debian testing/unstable)
>Organization:
Information System Development
>Environment:
System: Linux fluffy.isd.dp.ua 2.4.16 #2 Tue Dec 4 11:17:53 EET 2001 i686 unknown
Architecture: i686
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux
>Description:
I tried to build AT&T Cyclone 0.2 with gcc-3.0, and it trapped. Here is a sample to demonstrate an idea:
int main ()
{
int t[0] = {};
int *p=t;
}
Running gcc-3.0 sample.c
gives this:
sample.c: In function `main':
sample.c:4: 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.
gcc-2.95 and g++-3.0 compile the code withour problems.
>How-To-Repeat:
Just put these 5 lines of code in the file and compile it with gcc-3.0
No preprocessor involved.
>Fix:
AT&T Cyclone was succesfully compiled with gcc-2.95
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
@ 2001-12-07 16:46 rodrigc
0 siblings, 0 replies; 5+ messages in thread
From: rodrigc @ 2001-12-07 16:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/5041; it has been noted by GNATS.
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
mwg@fluffy.isd.dp.ua, nobody@gcc.gnu.org, serettov@hotmail.com,
reichelt@igpm.rwth-aachen.de, rodrigc@gcc.gnu.org,
sevillar@team.ph.inter.net
Cc:
Subject: Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
Date: 8 Dec 2001 00:42:19 -0000
Synopsis: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
State-Changed-From-To: analyzed->closed
State-Changed-By: rodrigc
State-Changed-When: Fri Dec 7 16:42:18 2001
State-Changed-Why:
Fixed in gcc 3.0.3:
http://gcc.gnu.org/ml/gcc-cvs/2001-12/msg00287.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5041&database=gcc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
@ 2001-12-07 16:42 rodrigc
0 siblings, 0 replies; 5+ messages in thread
From: rodrigc @ 2001-12-07 16:42 UTC (permalink / raw)
To: gcc-bugs, gcc-gnats, gcc-prs, mwg, nobody, serettov, reichelt,
rodrigc, sevillar
Synopsis: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
State-Changed-From-To: analyzed->closed
State-Changed-By: rodrigc
State-Changed-When: Fri Dec 7 16:42:18 2001
State-Changed-Why:
Fixed in gcc 3.0.3:
http://gcc.gnu.org/ml/gcc-cvs/2001-12/msg00287.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5041&database=gcc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
@ 2001-12-07 8:16 rodrigc
0 siblings, 0 replies; 5+ messages in thread
From: rodrigc @ 2001-12-07 8:16 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/5041; it has been noted by GNATS.
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
mwg@fluffy.isd.dp.ua, nobody@gcc.gnu.org
Cc:
Subject: Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
Date: 7 Dec 2001 16:07:13 -0000
Synopsis: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
State-Changed-From-To: open->analyzed
State-Changed-By: rodrigc
State-Changed-When: Fri Dec 7 08:07:12 2001
State-Changed-Why:
Fixed in gcc 3.1 mainline, but not in gcc 3.0 branch.
This needs to be merged to branch:
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg00841.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5041&database=gcc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
@ 2001-12-07 8:07 rodrigc
0 siblings, 0 replies; 5+ messages in thread
From: rodrigc @ 2001-12-07 8:07 UTC (permalink / raw)
To: gcc-bugs, gcc-gnats, gcc-prs, mwg, nobody
Synopsis: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault
State-Changed-From-To: open->analyzed
State-Changed-By: rodrigc
State-Changed-When: Fri Dec 7 08:07:12 2001
State-Changed-Why:
Fixed in gcc 3.1 mainline, but not in gcc 3.0 branch.
This needs to be merged to branch:
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg00841.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5041&database=gcc
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-12-08 0:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-07 5:56 c/5041: Zero-length arrays initialized by {}; cause gcc-3.0 to segfault mwg
2001-12-07 8:07 rodrigc
2001-12-07 8:16 rodrigc
2001-12-07 16:42 rodrigc
2001-12-07 16:46 rodrigc
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).