Re: GCC 8.4 Status Report (2020-02-17)

2020-02-23 Thread Jakub Jelinek
On Sun, Feb 23, 2020 at 08:25:32PM +0200, Thomas Backlund wrote: > Can this one be backported to gcc 8.4: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521 > > It fixes errors like: > https://travis-ci.org/akien-mga/godot/jobs/654085724 > > ./core/math/vector3.h:40:8: note: candidate: 'co

Re: GCC 8.4 Status Report (2020-02-17)

2020-02-23 Thread Thomas Backlund
Den 17-02-2020 kl. 12:45, skrev Jakub Jelinek: Status == It has been almost a year since GCC 8.3 has been released and GCC 8.4 release should have been released already, so we should concentrate on getting it out soon. Unfortunately we have two P1s, one of them is waiting for reporter's inp

Re: GCC 8.4 Status Report (2020-02-17)

2020-02-20 Thread Bernd Edlinger
On 2/19/20 10:24 AM, Richard Biener wrote: > On Tue, Feb 18, 2020 at 8:37 PM Bernd Edlinger > wrote: >> >>> It has been almost a year since GCC 8.3 has been released and GCC 8.4 >>> release should have been released already, so we should concentrate on >>> getting it out soon. Unfortunately we ha

Re: GCC 8.4 Status Report (2020-02-17)

2020-02-19 Thread Richard Biener
On Tue, Feb 18, 2020 at 8:37 PM Bernd Edlinger wrote: > > > It has been almost a year since GCC 8.3 has been released and GCC 8.4 > > release should have been released already, so we should concentrate on > > getting it out soon. Unfortunately we have two P1s, one of them is > > waiting for repor

Re: GCC 8.4 Status Report (2020-02-17)

2020-02-18 Thread Bernd Edlinger
> It has been almost a year since GCC 8.3 has been released and GCC 8.4 > release should have been released already, so we should concentrate on > getting it out soon. Unfortunately we have two P1s, one of them is > waiting for reporter's input, so we might as well just ignore it unless > the inpu

GCC 8.4 Status Report (2020-02-17)

2020-02-17 Thread Jakub Jelinek
Status == It has been almost a year since GCC 8.3 has been released and GCC 8.4 release should have been released already, so we should concentrate on getting it out soon. Unfortunately we have two P1s, one of them is waiting for reporter's input, so we might as well just ignore it unless the