Path: utzoo!telly!attcan!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ulysses.att.com!ekrell
From: ekrell@ulysses.att.com
Newsgroups: gnu.gcc.bug
Subject: Re: gcc 1.33 doesn't compile itself with stage2/gcc on a sun4os4 and -O
Message-ID: <8902041459.AA26199@hector.homer.nj.att.com>
Date: 4 Feb 89 14:59:20 GMT
References: <8902032233.AA00341@sugar-bombs.ai.mit.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 26

Let me explain myself. The Makefile distributed with gcc 1.33 uses CFLAGS=-g.
I changed this line to CFLAGS=-O. Then I run:

make
make stage1
make CC=stage1/gcc CFLAGS="-O -Bstage1/"
rm -fr stage1
make stage2
make CC=stage2/gcc CFLAGS="-O -Bstage2/"

at this point, I get a core dump from stage2/cc1 when compiling "toplev.c".

If I repeat this process without the -O, ie, CFLAGS= in the Makefile, and

make
make stage1
make CC=stage1/gcc CFLAGS=-Bstage1/
rm -fr stage1
make stage2
make CC=stage2/gcc CFLAGS=-Bstage2/

Then I don't get any core dump and the *.o files compare ok with the ones
in stage2/*.o

My interpretation of this is that the "stage1/gcc -O" phase generates
bad code which makes stage2/cc1 core dump on toplev.c.