The number of bugs targeted at GCC 4.1 has declined to 225 from 250 in my September 7th status report:
http://gcc.gnu.org/ml/gcc/2005-09/msg00179.html The number of critical (wrong-code, ice-on-valid, rejects-valid) regressions has declined to 61 from 77. So, we're still fixing about one net regression per day, and about 2/3rd of the regressions we're fixing are critical. Of the 61 critical bugs, about half (31) are 4.1 regressions, i.e., do not occur with 4.0. 18 of the critical bugs are C++; the rest are primarily middle-end optimizer problems. Since we're checking in something like 5 patches a day to gcc/, and we're in bug-fix mode, we're either fixing a lot of bugs that aren't regressions, or we're introducing a lot of bugs when we check in patches, or people are finding new regressions at a rate that exceeds our ability to fix them. It's time for a quality push so that we can actually get to 4.1. Starting Friday, at midnight PDT, the mainline will go to the mode normally used for branches: fixes for regressions only, including code-generation regressions. We will stay in that mode until we hit our 100-regression target. Then, we'll re-open briefly to allow any queued-up critical non-regression bug-fixes. Then we'll branch. All of the usual suspects (Berlin, Bosscher, Henderson, Hubicka, Mitchell, Novillo, etc.) have bugs with our names on them. I think we can knock quite a few these down relatively easily. -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
