Status
==
The GCC 4.3 branch is open for commits under normal release branch
rules. The 4.3.2 release was expected around 2008-08-06, but as
there are still P1s, it might be delayed a little bit.
Quality Data
Priority # Change from Last Report
---
Priority # Change from Last Report
--- ---
P13 - 5
P2 115 - 2
P32 - 1
--- ---
Total 120 - 8
PR35752, which is a P2 regression
As we are approaching the intended release date of 4.3.2 we need to
address the P1 bugs or downgrade them accordingly. Two of the P1s
have patches posted (more than 3 resp. 2 weeks ago), so they just
need reviewing.
For the record, these are:
Hi Paolo,
* Paolo Bonzini wrote on Thu, Jul 31, 2008 at 02:53:21PM CEST:
PR35752, which is a P2 regression caused by libtool, is waiting for
approval upstream. Should we make an exception to the usual rules and
apply the fix on the branch?
If by exception to the usual rule, you mean
Ralf Wildenhues wrote:
Hi Paolo,
* Paolo Bonzini wrote on Thu, Jul 31, 2008 at 02:53:21PM CEST:
PR35752, which is a P2 regression caused by libtool, is waiting for
approval upstream. Should we make an exception to the usual rules and
apply the fix on the branch?
If by exception to the
On Thu, Jul 31, 2008 at 03:10:46PM +0200, Paolo Bonzini wrote:
Ralf Wildenhues wrote:
Tomorrow it's a public holiday here, so I wouldn't apply the patch
before monday anyway.
If the patch is checked in on Monday or Tuesday, that's still fine,
no need to use exceptions.
Jakub
Paolo Bonzini wrote:
http://gcc.gnu.org/ml/gcc-patches/2008-06/msg01305.html
dwarf2out.c (CCing Jason Merrill)
That patch went in a while back, but your message led me to the one that
still needed reviewing. :)
Jason
