GCC 4.3.2 Status Report (2008-07-31)

GCC 4.3.2 Status Report (2008-07-31)

[Jakub Jelinek]

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
--------        ---     -----------------------
P1                3     -  5
P2              115     -  2
P3                2     -  1
--------        ---     -----------------------
Total           120     -  8


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.

If you think you have spotted a regression on the branch for a
primary or secondary target that does not show up when invoking the
"Serious regressions" link from the GCC homepage please tell one
of the RMs.


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

http://gcc.gnu.org/ml/gcc/2008-07/msg00240.html

The next report for the 4.3 branch will be sent by Mark.

Re: GCC 4.3.2 Status Report (2008-07-31)

[Paolo Bonzini]

> Priority          #     Change from Last Report
> --------        ---     -----------------------
> P1                3     -  5
> P2              115     -  2
> P3                2     -  1
> --------        ---     -----------------------
> Total           120     -  8

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?

Paolo

Re: GCC 4.3.2 Status Report (2008-07-31)

[Paolo Bonzini]

> 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:

http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00722.html
reload.c (CCing Ulrich Weigand)

http://gcc.gnu.org/ml/gcc-patches/2008-06/msg01305.html
dwarf2out.c (CCing Jason Merrill)

Paolo

Re: GCC 4.3.2 Status Report (2008-07-31)

[Ralf Wildenhues]

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 that you would like to apply
the patch to GCC before it's accepted in Libtool, then can you give me
24 hours, which may just be enough to not need to bend this particular
rule?

Thanks,
Ralf

Re: GCC 4.3.2 Status Report (2008-07-31)

[Paolo Bonzini]

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 usual rule, you mean that you would like to apply
> the patch to GCC before it's accepted in Libtool

And only on the branch.

Tomorrow it's a public holiday here, so I wouldn't apply the patch 
before monday anyway.

Paolo

Re: GCC 4.3.2 Status Report (2008-07-31)

[Jakub Jelinek]

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

Re: GCC 4.3.2 Status Report (2008-07-31)

[Jason Merrill]

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