Re: Implementing p0515 - spaceship operator

2018-01-08 Thread Jason Merrill
On Mon, Jan 8, 2018 at 5:13 PM, Jonathan Wakely wrote: > On 8 January 2018 at 22:07, Jason Merrill wrote: >> On Mon, Jan 8, 2018 at 4:07 PM, Tim van Deurzen wrote: >>> I've been spending some time the past few weeks implementing p0515r2, >>> i.e. the proposal for consistent comparisons for C++ (a

Re: Implementing p0515 - spaceship operator

2018-01-08 Thread Jonathan Wakely
On 8 January 2018 at 22:07, Jason Merrill wrote: > On Mon, Jan 8, 2018 at 4:07 PM, Tim van Deurzen wrote: >> I've been spending some time the past few weeks implementing p0515r2, >> i.e. the proposal for consistent comparisons for C++ (aka the spaceship >> operator). > > Great! > >> I've received

Re: Implementing p0515 - spaceship operator

2018-01-08 Thread Jason Merrill
On Mon, Jan 8, 2018 at 4:07 PM, Tim van Deurzen wrote: > I've been spending some time the past few weeks implementing p0515r2, > i.e. the proposal for consistent comparisons for C++ (aka the spaceship > operator). Great! > I've received some very valuable help on the IRC channel, but > I'm still

Implementing p0515 - spaceship operator

2018-01-08 Thread Tim van Deurzen
Hi, I've been spending some time the past few weeks implementing p0515r2, i.e. the proposal for consistent comparisons for C++ (aka the spaceship operator). I've received some very valuable help on the IRC channel, but I'm still a little bit stuck. Note, I'm completely new to the GCC codebase and

Re: GCC 8.0.0 Status Report (2018-01-08), Stage 3 ends Jan 14th

2018-01-08 Thread H.J. Lu
On Mon, Jan 8, 2018 at 4:13 AM, Richard Biener wrote: > > Status > == > > GCC 8 is in development stage 3 currently but that is going to end > at the end of Sunday, Jan 14th after which we go into regression > and documentation fixes mode similar as if trunk was a release branch. I'd like to

GCC 8.0.0 Status Report (2018-01-08), Stage 3 ends Jan 14th

2018-01-08 Thread Richard Biener
Status == GCC 8 is in development stage 3 currently but that is going to end at the end of Sunday, Jan 14th after which we go into regression and documentation fixes mode similar as if trunk was a release branch. We're still in pretty bad shape regression-wise but I hope things will get bett