> [ Updating Gcc to a newer version ]
> 
> > 2.7.0 also has a code generation problem in C++ on SPARC.  You will
> > see this if you compile eg. groff with it.  This is _not_ the
> > for-scope thing!  The resulting binaries will core-dump all the time;
> > at least on SunOS.
> 
> Hmm, that's news to me.  I'm using groff compiled SunOS binaries w/out
> any problems.  I did however need to do some hand-editing of files to
> get it to successfully compile in addtion to the CFLAGS additions for
> the 'for-scope thing'.  However, I no longer have access to the source
> on that machine anymore, so I can't tell you what they were.  It wasn't
> too hard though.

Strange...  I compiled it 4 times with 2.7.0, and every time the resulting
binaries core-dumped.  But only the C++ ones.  I then compiled with 2.6.3
and it worked right away.

However, this was _not_ a problem with eg. Fresco, which did compile and
did _not_ coredump, so...  I don't know.  I recall seeing a message about
this some time ago too, I think it was on one of the GCC lists.

Thorsten
--
Thorsten Lockert        | postmaster@sigmasoft.com | Universe, n.:
1262 Golden Gate Avenue | hostmaster@sigmasoft.com |         The problem.
San Francisco, CA 94115 | tholo@sigmasoft.com      |