This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Number of 3.3 hi-pri PRs going up
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 21 Feb 2003 09:48:59 -0800
- Subject: Re: Number of 3.3 hi-pri PRs going up
- References: <1045830003.730.188.camel@steven>
On Fri, Feb 21, 2003 at 01:20:03PM +0100, Steven Bosscher wrote:
>
> Just one week before the planned release of GCC 3.3, the number of
> high-priority bugs for 3.3 is going *up* instead of down!
>
> Mostly thanks to Wolfgang and Janis, for quite a few PRs the patches
> causing the bugs have been located. Unfortunately, hardly any of these
> PRs were picked up by by somebody for fixing.
Several other people have been helping out with this lately, too.
Fortunately, your statement about hardly any of these bugs being fixed
is not correct; quite a few of them have been fixed, some by the person
who introduced the regression and some by others. Here's a summary,
which is missing recent reports from other people:
regressions not yet fixed anywhere (besides the new parser) whose GNATS
entries identify the patch that introduced the regression
PR version reported submitter notes
8994 3.2/3.3 2002-12-18 jh
8964 3.3/3.4 2002-12-23 mark
8913 3.3 2002-12-12 jason
8906 3.2/3.3/3.4 2002-12-12 jason
8828 3.2/3.3 2002-12-24 jakub
8808 3.2/3.3 2002-12-18 jh
8730 3.2/3.3 2002-12-24 kenner intermittent failure
8634 3.2/3.3 2002-12-23 jh
8564 3.2/3.3/3.4 2002-12-12 jason
8555 3.2 2002-12-23 jakub
8442 3.4 2002-12-14 nathan
7916 3.2/3.3/3.4 2002-12-20 jh
7675 3.2/3.3/3.4 2002-12-24 jason
6387 3.2/3.3 2002-12-14 jakub
4382 3.2 2002-12-19 rth
regressions that exist only on branches whose GNATS entries identify the
patch that fixed the bug on the mainline
PR version reported submitter notes
9183 3.2 2003-01-14 mark gigantic patch
8582 3.2 2002-12-20 jason
8205 3.2 2002-12-23 nathan/mark
8117 3.2 2002-12-13 nathan/mark
8116 3.2 2002-12-23 nathan
7247 3.2 2003-01-14 dberlin/dann
fixed or otherwise closed after cause was reported; thanks!
PR reported fixed fixer
9342 2003-01-16 2003-01-17 jason
9258 2003-01-14 2003-02-15 jh
9167 2003-01-06 2003-01-17 jason
9165 2003-01-06 2003-01-07 mark
8849 2002-12-19 2003-01-31 lerdsuwa
8848 2002-12-12 2003-01-20 rth
8702 2002-12-16 2002-12-24 nathan
8602 2003-01-15 2003-02-24 rth
8572 2002-12-11 2002-12-22 nathan
8492 2002-12-20 2003-01-22 jh
7964 2002-12-17 2002-12-24 nathan
7782 2002-12-11 2003-01-08 jh
7154 2002-12-17 2003-01-20 rth
9013 2003-01-15 closed fixed?
8917 2002-12-16 closed duplicate of 8913
7949 2003-01-06 closed not a bug
7687 2002-12-20 closed will not be fixed for branch
> So please help bug-fixing. This will not only help 3.3 but 3.4 as well
> because so many bugs are present on both the release branch and the
> trunk. So even if 3.4 is more interesting to you, locating and/or
> fixing bugs for 3.3 will be beneficial to you as well.
I'll run some more regression hunts for regressions in 3.3. This is now
a background task that takes just a few minutes of work for each PR,
plus a couple of hours of elapsed time, to identify the patch.
Janis