Re: GCC Release Status (2003-09-05)

[Jan Hubicka <hubicka at ucw dot cz>]

> 
> GCC 3.3.2
> =========
> 
> GCC 3.3.2 is tentatively scheduled for October 1, 2003, which is 25
> days away.
> 
> There are presently 96 bugs (down from 101).  I reviewed every last
> one last night and downgraded/closed a bunch.  Most of these are
> pretty obscure, but a few are pretty important, and a bunch of those
> have Jan Hubicka's name next to them.  Jan, pelase let me know ASAP
> what the status on the bugs assigned to you is.

8126 - as discussed last time, the problem is dificult to fix as it lies
       in random code quality produced by reg-stack pass
9929 - there is waiting fix for that
       http://gcc.gnu.org/ml/gcc-patches/2003-05/msg02107.html
This is everything related to 3.3 I get when I search for my name in
assigned field.  Did I miss some?
There are several SSE related bugs not makred as regression.  I fixed
them in mainline and I am not sure we want the patches in 3.3.2 as
techically they are not regression when code din't work at all.

Honza
> 
> It also looks like -fnon-call-exceptions has issues.
> 
> C++ continues to be a problem, with 23 open bugs.
> 
> GCC 3.4
> =======
> 
> GCC 3.4 is in Stage 2.  GCC 3.4 will enter Stage 3 (bugfixes only) on
> October 15th, which is 39 days away.
> 
> There are 143 bugs targeted for GCC 3.4 (down from 331).  That sharp
> decrease represents the work of our bug volunteers (thanks!!) who went
> through and removed non-regressions from the list.  44 of those bugs
> are C++ bugs; the corner cases are still getting flushed out of the
> new parser.  Some of these are diagnostic-related; I am not too
> sympathetic to some, but not all, of these complaints.
> 
> There are 26 optimization bugs and 15 target-specific bugs.
> 
> Previous Status Report
> ======================
> 
> http://gcc.gnu.org/ml/gcc/2003-08/msg01339.html
> 
> --
> Mark Mitchell
> CodeSourcery, LLC
> mark@codesourcery.com