gcc-2.95 status

[Marc Espie]

In article < 4032.930228776@upchuck.cygnus.com > you write:
>
>
>Just to let folks who do not read the schedule & regression status pages
>know where we stand on the gcc-2.95 release.
>
>The critical bugfreeze date was originally scheduled for July 15th.  We
>slipped that 1 week to July 22 to give us more time to address some of the
>problems encountered during testing.

>Since we are now past the critical bug-freeze date we are only accepting
>patches for critical bugs and all patches have to be run by me before
>they are to be installed on the gcc-2.95 branch.


There's still some highly critical stuff for me. I'd really like m68k
pic to work a little bit more reliably for floating point.

This is a large, critical problem for OpenBSD... we'd rather not put the m68k
platforms in the list of `dead' machines, but we can't really ship releases
with two distinct compilers with different features.

See http://egcs.cygnus.com/ml/egcs-bugs/1999-05/msg00764.html
for an example of how critical it is.

I must stress that if this bug remains in gcc 2.95, there's a chance we will
have to revert our recent changes and ship the next OpenBSD release with
gcc 2.8.1 (as you know, egcs 1.1 is unsuitable for us, since code bloat is
an issue for boot floppies) :(

There's also that netbsd sparc problem I forwarded to the list, with a
potential fix (removing some egcs-1.1.2 code, 
http://egcs.cygnus.com/ml/egcs-bugs/1999-06/msg00238.html )

I'm available for helping checking/elucidating stuff, but I'm nowhere near the
level of analysing and fixing those problems... 
... plus, I still have quite a few linker/assembler related problems to fix,
and a bunch of ports to adapt to g++-2.95...