Path: utzoo!telly!attcan!dptcdc!jarvis.csri.toronto.edu!mailrus!cwjcc!ukma!xanth!uunet!cacilj!paul
From: paul@cacilj.UUCP (Paul Close)
Newsgroups: gnu.gcc.bug
Subject: Re: gcc 1.33 (sparc, SunOS 4.0) bombs (IMPORTANT UPDATE!)
Message-ID: <896@cacilj.UUCP>
Date: 13 Feb 89 20:38:00 GMT
References: <893@cacilj.UUCP>
Reply-To: paul@cacilj.UUCP (Paul Close)
Organization: CACI Products Company, La Jolla, CA
Lines: 16

In article <893@cacilj.UUCP> I write:
| I am confirming what has already been posted here:  the cc1 program in
| stage2 blows up on several files with signals 6 or 11.  I used optimization
| only with gcc; I used no flags with the plain cc.  The object files that
| *were* produced compared perfectly.

| There are 14 failures: 6 SIGABRT (abort), 8 SIGSEGV (segmentation violations).

I have found that this problem occurs when I compile using
CFLAGS="-O -Bstage(n)/", but NOT when CFLAGS="-g -O -Bstage(n)/".  Definitely
sounds fishy....  Seems like somehow the -g flag modifies the -O flag's
behaviour.
-- 
Paul Close	paul@cacilj.CTS.COM 	...!{uunet, ucsd, crash}!cacilj!paul

    The Obi-wan Kenobi method:  "Use the Source, Luke"	-Jim Fulton