GCC 7.0.1 Status Report (2017-04-20)

GCC 7.0.1 Status Report (2017-04-20)

[Jakub Jelinek]

Status
======

We have reached zero P1 regressions today (and < 100 important
regressions) and the branches/gcc-7-branch has been created;
GCC 7.1-rc1 will be built and announced likely tomorrow.
The branch is now frozen for blocking regressions and documentation
fixes only, all changes to the branch require a RM approval now.

If no show stoppers appear, we'd like to release 7.1 late next week,
or soon after that, if any important issues are discovered and
fixed, rc2 could be released next week.

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

Priority          #   Change from last report
--------        ---   -----------------------
P1                0   -  17
P2               96   -  12
P3                3   -  16
P4		147   +   9
P5		 29   -   1
--------        ---   -----------------------
Total P1-P3      99   -  45
Total		275   -  37


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

https://gcc.gnu.org/ml/gcc/2017-03/msg00066.html

Re: GCC 7.0.1 Status Report (2017-04-20)

[Andreas Krebbel]

On 04/20/2017 12:02 PM, Jakub Jelinek wrote:
> Status
> ======
> 
> We have reached zero P1 regressions today (and < 100 important
> regressions) and the branches/gcc-7-branch has been created;
> GCC 7.1-rc1 will be built and announced likely tomorrow.
> The branch is now frozen for blocking regressions and documentation
> fixes only, all changes to the branch require a RM approval now.

I would like to apply the following patches to GCC 7 release branch before the 7.1 release:

It took us a few more review cycles than expected.  The patches are important to get reasonable code
for the C11 atomics now being used in Glibc:

S/390: Optimize atomic_compare_exchange and atomic_compare builtins.
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00524.html

These fixes for two GCC 7 regressions:

S/390: PR80464: Split MEM->GPR vector moves
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01050.html

S/390: PR79895: Fix TImode constant handling
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01049.html

Any objections?

-Andreas-

Re: GCC 7.0.1 Status Report (2017-04-20)

[Jakub Jelinek]

On Mon, Apr 24, 2017 at 06:08:15PM +0200, Andreas Krebbel wrote:
> On 04/20/2017 12:02 PM, Jakub Jelinek wrote:
> > Status
> > ======
> > 
> > We have reached zero P1 regressions today (and < 100 important
> > regressions) and the branches/gcc-7-branch has been created;
> > GCC 7.1-rc1 will be built and announced likely tomorrow.
> > The branch is now frozen for blocking regressions and documentation
> > fixes only, all changes to the branch require a RM approval now.
> 
> I would like to apply the following patches to GCC 7 release branch before the 7.1 release:
> 
> It took us a few more review cycles than expected.  The patches are important to get reasonable code
> for the C11 atomics now being used in Glibc:
> 
> S/390: Optimize atomic_compare_exchange and atomic_compare builtins.
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00524.html
> 
> These fixes for two GCC 7 regressions:
> 
> S/390: PR80464: Split MEM->GPR vector moves
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01050.html
> 
> S/390: PR79895: Fix TImode constant handling
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01049.html
> 
> Any objections?

Ok for 7.1, but only if you manage to commit before rc1 is rolled
(still waiting for the ARM/AArch64 ABI finalization there),
otherwise wait for 7.2.

	Jakub

Re: GCC 7.0.1 Status Report (2017-04-20)

[Andreas Krebbel]

On 04/25/2017 12:25 PM, Jakub Jelinek wrote:
> On Mon, Apr 24, 2017 at 06:08:15PM +0200, Andreas Krebbel wrote:
>> On 04/20/2017 12:02 PM, Jakub Jelinek wrote:
>>> Status
>>> ======
>>>
>>> We have reached zero P1 regressions today (and < 100 important
>>> regressions) and the branches/gcc-7-branch has been created;
>>> GCC 7.1-rc1 will be built and announced likely tomorrow.
>>> The branch is now frozen for blocking regressions and documentation
>>> fixes only, all changes to the branch require a RM approval now.
>>
>> I would like to apply the following patches to GCC 7 release branch before the 7.1 release:
>>
>> It took us a few more review cycles than expected.  The patches are important to get reasonable code
>> for the C11 atomics now being used in Glibc:
>>
>> S/390: Optimize atomic_compare_exchange and atomic_compare builtins.
>> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00524.html
>>
>> These fixes for two GCC 7 regressions:
>>
>> S/390: PR80464: Split MEM->GPR vector moves
>> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01050.html
>>
>> S/390: PR79895: Fix TImode constant handling
>> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01049.html
>>
>> Any objections?
> 
> Ok for 7.1, but only if you manage to commit before rc1 is rolled
> (still waiting for the ARM/AArch64 ABI finalization there),
> otherwise wait for 7.2.

Ok. Done.

-Andreas-