This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.1 Release
- From: Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: mark at codesourcery dot com, gcc at gcc dot gnu dot org
- Date: Wed, 3 Apr 2002 12:35:30 +0200
- Subject: Re: GCC 3.1 Release
Hello,
Mark Mitchell wrote:
> Now that Richard has made GNATS immune to random new bugs being classified
> as "high" priority, it makes sense to go back to using high-priority bugs
> in GNATS -- rather than an external issuse list -- as our way to measure
> what needs to be done before the release.
>
> To that end, I've made sure that everything on the issues list is marked
> "high" in GNATS, and checked in a new copy of the issues list that
> indicates it is no longer in use.
>
> Now we need to weed out any not-really-high-priority bugs in GNATS, and
> fix what's there.
Last month I posted a list with several regressions from gcc 3.0.x and 2.95.x,
see http://gcc.gnu.org/ml/gcc/2002-03/msg00387.html
For some reason however, the bugs never made it to the 3.1-issues list.
Maybe it would be a good idea to mark some of them "high priority" in GNATS
(at least those that are not ice-on-illegal-code).
A slightly updated list for your convenience:
* Regressions from 3.0.4:
5078 ice-on-legal-code
5565 ice-on-illegal-code
5656 ice-on-illegal-code
5657 ice-on-illegal-code
5666 ice-on-illegal-code
5921 ice-on-illegal-code (wasn't included in the original list -
might be worth a "high priority" mark although
it is an ice-on-illegal-code, see
http://gcc.gnu.org/ml/gcc/2002-03/msg00449.html
for more information)
* Regressions from 2.95.3 that haven't been fixed in 3.0.x and are
still present in the 3.1 branch:
4934 ice-on-legal-code
4954/5052 ice-on-legal-code
4979 ice-on-legal-code
5189 ice-on-legal-code
5571 ice-on-legal-code
I removed PR 4757 from the list because the bug was already present in gcc 2.95.2.
Greetings,
Volker Reichelt