[PPL-devel] [Fwd: GCC 4.4.0 Status Report (2008-11-01)]

[Roberto Bagnara]

-------- Original Message --------
Subject: GCC 4.4.0 Status Report (2008-11-01)
Date: Sat, 1 Nov 2008 13:16:05 +0100 (CET)
From: Richard Guenther <rguenther at suse dot de>
To: gcc at gcc dot gnu dot org
CC: Jakub Jelinek <jakub at redhat dot com>

Status
======

The two months of Stage 3 have ended and the trunk is now in regression
and documentation fixes only mode.

At this point bugfixing should concentrate on getting the list of serious
regressions down to a level that makes GCC 4.4 ready to release.
As an exception to this we will still have the old register allocator
removed before we branch for the GCC 4.4.0 release.  As usual
maintainers may consider fixing serious bugs such as rejection of
valid code or wrong-code bugs appropriate even if they are not regressions.

The two quality metrics you know from the past still apply.  We will
consider releasing GCC 4.4.0 once the number of serious regressions
is below 100 and no more P1 regressions remain.  Only after releasing
GCC 4.4.0 we will branch and open Stage 1 for GCC 4.5 development.
Past experience tells us that we can expect this to happen not before
another two months pass, which would be early next year.

Quality Data
============

Priority	  #	Change from Last Report
--------	---	-----------------------
P1		 17     -  9
P2		141 	+  8
P3		  3	+  1
--------	---	-----------------------
Total		161	+- 0

We seem to make good progress in tackling P1 bugs though the overall
number of serious regressions didn't decline.  Which probably means
we are getting more testing coverage now, which is good.

I encourage maintainers to look over the bugs in their respective
area and make sure we do not miss regressions that are not marked
appropriately ([X.Y Regression] in the summary and a target milestone
of the next version of the oldest active branch affected).  In case
you think a bug is not appropriately prioritized bump the priority
back to P3 which makes the release managers aware of it.

Note that P3 means un-prioritized and that only bugs for C, C++ and
their runtimes for the list of primary and secondary targets listed
at http://gcc.gnu.org/gcc-4.4/criteria.html qualify for P1 or P2.

Previous Report
===============

http://gcc.gnu.org/ml/gcc/2008-10/msg00404.html

The next report for 4.4.0 will be sent by Jakub.

-- 
Richard Guenther <rguenther at suse.de>
Novell / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex


-- 
Prof. Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy
http://www.cs.unipr.it/~bagnara/
mailto:bagnara at cs.unipr.it