gcc-2.95 status

[Jeffrey A Law]

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.

--

We also slipped the proposed release date by one week from July 1 to July 8.

-


Outstanding testing related issues for the release (ie, stuff you can help 
with!)

  Regressions on i686-pc-sco3.2v5.0.5.  Robert Lipe is currently on vacation,
  but returns July 1 I believe.  I'm going to try and simulate some of those
  failures by building a Linux system with dwarf1 debug symbols by default.
  Otherwise we'll have to wait for Robert to return before we can attack these
  problems.

  We need libg++ tested on the following platforms:

   i686-pc-sco3.2v5.0.5 (Robert Lipe)
   i686-pc-linux-gnulibc1


  libgcj/libjava has exposed a compiler bug on mips-sgi-irix6.5 that needs
  to be fixed.  Other build failures have been libgcj portability problems.
  libgjc/libjava build issues will not hold up the release unless they are
  compiler bugs.

  glibc-2.1.1 needs to be built & tested on a sparc-linux machine.  Alexandre
  Oliva is taking care of this.

  linux-2.2.10 needs to be built installed and booted on an alpha, powerpc and
  sparc system.  Note that you should build the kernel "-fno-strict-aliasing".


  The few remaining failures for a redhat-6.0 build on the x86 need to
  be resolved.  If someone wants to do redhat-6.0 builds on one of the other
  processors it supports, please do so and let me know the results.  Note
  several C++ packages need "-fpermissive" to build.

  Any additional Fortran and C++ testing needs to be hashed out in the very
  near future.  ie, what package, where can folks get it, how to build and
  test, etc.


There's still a few non-testing related bugs that need to be fixed.  I'll
be making a pass over my pending bugs directory this weekend to flush the
critical ones out and try to nail them down.


We're in the home stretch.  I'd like to thank everyone that has contributed
fixes, test results, bug analysis, build reports, etc etc.  Believe me, none
of this would be possible without your help.

jeff