GCC 9.3 Status Report (2020-03-05)

GCC 9.3 Status Report (2020-03-05)

[Jakub Jelinek]

Status
======

The GCC 9 branch is now frozen for blocking regressions and documentation
fixes only, all changes to the branch require a RM approval now.


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

Priority          #   Change from last report
--------        ---   -----------------------
P1                0
P2              226   -  17
P3               37   +   2
P4              168   -   1
P5               23
--------        ---   -----------------------
Total P1-P3     263   -  15
Total           454   -  16


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

https://gcc.gnu.org/ml/gcc/2020-02/msg00238.html

Re: GCC 9.3 Status Report (2020-03-05)

[Jonathan Wakely]

On Thu, 5 Mar 2020 at 20:23, Jakub Jelinek wrote:
>
> Status
> ======
>
> The GCC 9 branch is now frozen for blocking regressions and documentation
> fixes only, all changes to the branch require a RM approval now.

I'd like to backport https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00361.html

The only affected target I'm aware of is darwin8, which is an old
release. I could wait for after the 9.3 release, but it seems safe to
do now.

Re: GCC 9.3 Status Report (2020-03-05)

[Jakub Jelinek]

On Fri, Mar 06, 2020 at 12:12:09PM +0000, Jonathan Wakely wrote:
> On Thu, 5 Mar 2020 at 20:23, Jakub Jelinek wrote:
> >
> > Status
> > ======
> >
> > The GCC 9 branch is now frozen for blocking regressions and documentation
> > fixes only, all changes to the branch require a RM approval now.
> 
> I'd like to backport https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00361.html
> 
> The only affected target I'm aware of is darwin8, which is an old
> release. I could wait for after the 9.3 release, but it seems safe to
> do now.

Ok.
Seems to be of the wouldn't compile at all without the fix category, I think
we don't need another rc for this.

	Jakub

Re: GCC 9.3 Status Report (2020-03-05)

[Jonathan Wakely]

On Fri, 6 Mar 2020 at 12:18, Jakub Jelinek wrote:
>
> On Fri, Mar 06, 2020 at 12:12:09PM +0000, Jonathan Wakely wrote:
> > On Thu, 5 Mar 2020 at 20:23, Jakub Jelinek wrote:
> > >
> > > Status
> > > ======
> > >
> > > The GCC 9 branch is now frozen for blocking regressions and documentation
> > > fixes only, all changes to the branch require a RM approval now.
> >
> > I'd like to backport https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00361.html

Oops, that commit has the wrong PR number. It's for 94069.

> > The only affected target I'm aware of is darwin8, which is an old
> > release. I could wait for after the 9.3 release, but it seems safe to
> > do now.
>
> Ok.
> Seems to be of the wouldn't compile at all without the fix category, I think

Right.

> we don't need another rc for this.

OK, I'll do the backport today. Thanks.

Re: GCC 9.3 Status Report (2020-03-05)

[Jonathan Wakely]

On Thu, 5 Mar 2020 at 20:23, Jakub Jelinek wrote:
>
> Status
> ======
>
> The GCC 9 branch is now frozen for blocking regressions and documentation
> fixes only, all changes to the branch require a RM approval now.

I'd also like to backport this one:
https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00360.html

It only affects the testsuite (and only for *-*-mingw* targets), but
ensures we don't get FAILs caused by the tests hitting a different
bug.

Fixing that other bug will happen for 9.4, but we can avoid the
failures with a small tweak to the tests, so they still verify what
was intended. On the other hand, some failing tests won't actually
hurt the quality of the 9.3 release, so it's not important.

Re: GCC 9.3 Status Report (2020-03-05)

[Jakub Jelinek]

On Fri, Mar 06, 2020 at 12:35:09PM +0000, Jonathan Wakely wrote:
> > The GCC 9 branch is now frozen for blocking regressions and documentation
> > fixes only, all changes to the branch require a RM approval now.
> 
> I'd also like to backport this one:
> https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00360.html
> 
> It only affects the testsuite (and only for *-*-mingw* targets), but
> ensures we don't get FAILs caused by the tests hitting a different
> bug.
> 
> Fixing that other bug will happen for 9.4, but we can avoid the
> failures with a small tweak to the tests, so they still verify what
> was intended. On the other hand, some failing tests won't actually
> hurt the quality of the 9.3 release, so it's not important.

I think this isn't urgent enough and can wait for 9.4.  We don't guarantee
zero FAILs...

	Jakub

Re: GCC 9.3 Status Report (2020-03-05)

[Richard Earnshaw]

On 05/03/2020 20:22, Jakub Jelinek wrote:
> Status
> ======
> 
> The GCC 9 branch is now frozen for blocking regressions and documentation
> fixes only, all changes to the branch require a RM approval now.
> 
> 
> Quality Data
> ============
> 
> Priority          #   Change from last report
> --------        ---   -----------------------
> P1                0
> P2              226   -  17
> P3               37   +   2
> P4              168   -   1
> P5               23
> --------        ---   -----------------------
> Total P1-P3     263   -  15
> Total           454   -  16
> 
> 
> Previous Report
> ===============
> 
> https://gcc.gnu.org/ml/gcc/2020-02/msg00238.html
> 

I have the backport for PR91913 ready if you want it (fully 
bootstrapped), but it's only a P2, so can probably wait unless you're 
planning another RC.

R.