Re: GCC 9.3 Status Report (2020-03-05)
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)
On Fri, Mar 06, 2020 at 12:12:09PM +, 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)
On Fri, 6 Mar 2020 at 12:18, Jakub Jelinek wrote: > > On Fri, Mar 06, 2020 at 12:12:09PM +, 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)
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)
On Fri, Mar 06, 2020 at 12:35:09PM +, 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)
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 --- --- P10 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.
Re: GCC 9.3 Release Candidate available from gcc.gnu.org
On 2020-03-05 14:13, Jakub Jelinek wrote: The first release candidate for GCC 9.3 is available from https://gcc.gnu.org/pub/gcc/snapshots/9.3.0-RC-20200305/ ftp://gcc.gnu.org/pub/gcc/snapshots/9.3.0-RC-20200305/ and shortly its mirrors. It has been generated from git commit r9-8351-ge50627ff8cd54c3983614b34727323b333b9374d. I have so far bootstrapped and tested the release candidate on x86_64-linux and i686-linux. Please test it and report any issues to bugzilla. If all goes well, I'd like to release 9.3 on Thursday, March 12th. I bootstrapped and tested on power 7 and 8 BE and power 8 and 9 LE and saw nothing untoward. -- -Bill Seurer
gcc-8-20200306 is now available
Snapshot gcc-8-20200306 is now available on https://gcc.gnu.org/pub/gcc/snapshots/8-20200306/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-8 revision ce1281ffc193af8ef7c599bc84a91c320a9b18ed You'll find: gcc-8-20200306.tar.xzComplete GCC SHA256=965735cf72ba90cc7d40809ad61064aea6a0483f483378d59d1124d485df53b7 SHA1=cfe34b9d15a6476fedaf38b47978b4976a67f78a Diffs from 8-20200228 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-8 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
