c/5481: AT&T Cyclone compiles wrongly and segfaults

Wladimir Mutel mwg@fluffy.isd.dp.ua
Thu Jan 24 13:38:00 GMT 2002

>Number:         5481
>Category:       c
>Synopsis:       Making Cyclone 0.2 with gcc-3.0.3 compiler produces bad cyclone compiler executable.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 24 12:26:01 PST 2002
>Originator:     Wladimir Mutel
>Release:        3.0.3 (Debian testing/unstable)
System: Linux fluffy.isd.dp.ua 2.4.17 #1 Mon Dec 24 13:13:11 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

	During make, compiled and linked cyclone tries to compile bison/main.cyc
	cyclone segfaults


	Download http://www.research.att.com/projects/cyclone/cyclone-0.2.tar.gz
	Then do the following : 
	tar zxf cyclone-0.2.tar.gz
	cd cyclone
	vi Makefile.inc
		(change CC variable to be gcc-3.0, then save file and exit vi)

	Then you see this :
	make[1]: Entering directory `/disk1/home/mwg/cyclone/cyclone/tools/bison'
	/disk1/home/mwg/cyclone/cyclone/bin/cyclone  -I/disk1/home/mwg/cyclone/cyclone/include -B/disk1/home/mwg/cyclone/cyclone/bin/cyc-lib  -c main.cyc
	make[1]: *** [main.o] Segmentation fault
	make[1]: Leaving directory `/disk1/home/mwg/cyclone/cyclone/tools/bison'
	make: *** [tools] Error 2

	I tried to debug this, but without much success. I did not understand its logic completely enough, so I was unable to compose short enough testcase for gcc-3.0

	Compiling with gcc-2.95.4 works well. People from AT&T say that gcc-3.0 will not work.


More information about the Gcc-bugs mailing list