Re: GCC 3.4 Release Status (2003-12-16)

[Andrew Pinski <pinskia at physics dot uc dot edu>]

On Dec 16, 2003, at 09:32, Mark Mitchell wrote:
> GCC 3.4
> =======
>
> GCC 3.4 has, at this point, a ways to go.
>
> There are 186 bugs in bugzilla targeted for GCC 3.4, and that,
> historically means months of effort.  There are about 50 C++ bugs, but
> that number is falling rapidly.  There are about 40
> optimization/middle-end bugs.  We have 13 "debug" regressions.

Well things have improved in 3 days by Mark and others fixing some 
regressions and by me
moving non-regressions from bugs targeted for GCC 3.4 and finding 
already fixed bugs.
There are currently 136 bugs target for 3.4 out of which there are 10 
with patches waiting
for or have been approved already posted to gcc-patches, several more 
have patches in the
bug waiting to be reviewed.

Also the 136 does not include the bugs targeted for 3.3.3 which are not 
fixed for 3.4, 37 or 38 bugs.

4 are in WAITING to see if they have been fixed already in 3.4 by 
different patches.

3 are Unconfirmed, one is a regression for sure, another is an ABI bug.

41 now are assigned now:
Zack: 8
Jan: 5
Nathan: 5
Gaby: 3
Paolo: 3
Eric: 2
Jason: 2


Here I brake it down into each component:
7 bootstrap
13 C problems.
38 C++ ones.
9 debug.
2 driver
3 fortran (of which one has a patch and another is waiting for what is 
the correct answer)
1 inline-asm problem (just an ice-on-invalid)
6 java/libgcj
5 libstdc++ (out of which 3 are assigned)
3 middle-end problems
27 optimization bugs
3 preprocessor
14 targets (3 are not regressions but they are assigned or have small 
patches)
1 PCH/host problem
4 others


Thanks,
Andrew Pinski