GCC 8.3 Status Report (2019-02-08)
Status == GCC 7.3 has been released on January 25th, so it is about time to do GCC 8.3 release now. Unfortunately we have a recent P1 C++ regression - PR88995. Nathan (or Jason), do you think it can be fixed soon? In the meantime, can people with backportable patches backport fixes to 8.3, so that we can release a rc1 soon and do a release a week afterwards? Quality Data Priority # Change from last report --- --- P11 + 1 P2 197 + 84 P3 28 - 15 P4 165 - 14 P5 24 - 2 --- --- Total P1-P3 226 + 70 Total 415 + 54 Previous Report === https://gcc.gnu.org/ml/gcc/2018-07/msg00379.html
GCC 9 Status Report (2019-02-08)
Status
==
We're one month into the stabilization phase (Stage 4), making some
good progress in the long march towards zero P1 regressions. Please
have a look at those that you assigned yourself to.
As usual this is a good time to test your non-{primary,secondary}
target making sure it builds and works correctly.
Quality Data
Priority # Change from last report
--- ---
P1 24 - 18
P2 185 - 2
P3 32 - 15
P4 169 - 13
P5 24 - 1
--- ---
Total P1-P3 241 - 35
Total 434 - 49
Previous Report
===
https://gcc.gnu.org/ml/gcc/2019-01/msg00027.html
Re: gcc 8.3 estimated release date?
On Thu, 7 Feb 2019 at 21:16, John Marino wrote: > > Hi Guys, > I guess back in July, the release of 8.3 was expected by the end of > 2018. Now it's February. Is the next release of the 8 series imminent? > if not, any idea when it might come? See https://gcc.gnu.org/ml/gcc/2019-02/msg00027.html sent a few hours after your mail.
Re: GCC 8.3 Status Report (2019-02-08)
On 2/8/19 3:15 AM, Jakub Jelinek wrote: Status == GCC 7.3 has been released on January 25th, so it is about time to do GCC 8.3 release now. Unfortunately we have a recent P1 C++ regression - PR88995. Nathan (or Jason), do you think it can be fixed soon? In the meantime, can people with backportable patches backport fixes to 8.3, so that we can release a rc1 soon and do a release a week afterwards? Ah, I see I caused that by r268029, fixing some other PR. I did have a look, but didn't have sufficient time to investigate fully. a) revert the breaking fix, but IIRC that was also fixing a regression? b) perhaps we shouldn't be sending non-dependent expressions through the capture machinery, but instead wrapping them in an appropriate view_convert_expr to make them const? nathan -- Nathan Sidwell
Andrew Stubbs and Julian Brown appointed AMD GCN maintainers
I am pleased to announce that the GCC Steering Committee has appointed Andrew Stubbs and Julian Brown as AMD GCN maintainers. Please join me in congratulating Andrew and Julian on their new role. Andrew and Julian, please update your listings in the MAINTAINERS file. Happy hacking! David
Re: GCC 8.3 Status Report (2019-02-08)
On Fri, Feb 8, 2019 at 6:50 AM Nathan Sidwell wrote: > > On 2/8/19 3:15 AM, Jakub Jelinek wrote: > > Status > > == > > > > GCC 7.3 has been released on January 25th, so it is about time to do > > GCC 8.3 release now. Unfortunately we have a recent P1 C++ regression > > - PR88995. Nathan (or Jason), do you think it can be fixed soon? I think it was fixed by the patch for 88761 I just checked in. Jason > b) perhaps we shouldn't be sending non-dependent expressions through the > capture machinery, but instead wrapping them in an appropriate > view_convert_expr to make them const? > > > nathan > > -- > Nathan Sidwell
gcc-8-20190208 is now available
Snapshot gcc-8-20190208 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190208/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8-branch revision 268708 You'll find: gcc-8-20190208.tar.xzComplete GCC SHA256=3bd92378d994af807cbf34b68e08bb130568e4e1790ecf2abc210f0611e60904 SHA1=710b891502536681b9359c52a0febde2842af0c6 Diffs from 8-20190201 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.
