> :   I'm not trying to bash the core team, I'm just frustrated that I have to
> : maintain two versions of gcc with limited disk space.  I realize that gcc
> : often adds many new bugs in new releases, but I don't see why 2.5.8, 2.6.3
> : or 2.7.0, all of which were said to be very stable releases were not
> : integrated.  
> 
> 2.7.0 had a bug which made it choke on the mroute.c file (when trying to
> initializa a static struct as far as I remember) a couple of weeks ago. 
> I tried that myself.

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.  This did not happen
with 2.6.3...  So I suggest we at least wait till 2.7.1.  I would, however,
dearly want to have some 2.7.x version integrated, not the least because of all
the C++ fixes relative to 2.[456].x...

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