GCC 8.0.0 Status Report (2018-01-08), Stage 3 ends Jan 14th
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 better once we transition into stage 3. Note that the high number of unprioritized bugs (P3) means the actual priority distribution doesn't reflect reality. I'm going to work on this throughout the week dependent on bugzilla speed. Quality Data Priority # Change from last report --- --- P19 - 5 P2 134 - 27 P3 108 - 55 P4 161 + 27 P5 27 --- --- Total P1-P3 251 - 87 Total 355 - 60 Previous Report === https://gcc.gnu.org/ml/gcc/2017-11/msg00134.html
Re: GCC 8.0.0 Status Report (2018-01-08), Stage 3 ends Jan 14th
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 get my patches for CVE-2017-5715, aka Spectre, into GCC 8. > We're still in pretty bad shape regression-wise but I hope things will > get better once we transition into stage 3. Note that the high number > of unprioritized bugs (P3) means the actual priority distribution > doesn't reflect reality. I'm going to work on this throughout the > week dependent on bugzilla speed. > > > Quality Data > > > Priority # Change from last report > --- --- > P19 - 5 > P2 134 - 27 > P3 108 - 55 > P4 161 + 27 > P5 27 > --- --- > Total P1-P3 251 - 87 > Total 355 - 60 > > > Previous Report > === > > https://gcc.gnu.org/ml/gcc/2017-11/msg00134.html -- H.J.
Implementing p0515 - spaceship operator
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 am very much still getting oriented. Following advice from some of the people in IRC channel I implemented parsing the new token in libcpp and I seem to be successfully parsing it and creating a new AST node. As this feature is not in the C++ standard yet, I wanted to add a command line flag to enable usage of the new operator and ignoring it otherwise. I managed to get cc1plus to accept the parameter, but it seems that when I invoke my own g++ binary with that parameter, it complains about unknown parameters. I'm perfectly happy to dig further on my own, but I get the feeling I'm missing some documentation / resource somewhere that might help me out. Is there some documentation about adding and passing around parameters that will be used both in libcpp and the C++ front-end? What would be the best place to look to learn more about how part of GCC this is structured? I want to make sure I go about this correctly. If this is the wrong place to ask for help, please redirect me, so that I don't unnecessarily spam the wrong mailing list :-). Kind regards, Tim.
Re: Implementing p0515 - spaceship operator
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 a little bit stuck. Note, I'm completely new to the GCC > codebase and am very much still getting oriented. > > Following advice from some of the people in IRC channel I implemented > parsing the new token in libcpp and I seem to be successfully parsing it > and creating a new AST node. As this feature is not in the C++ standard > yet, I wanted to add a command line flag to enable usage of the new > operator and ignoring it otherwise. I managed to get cc1plus to accept > the parameter, but it seems that when I invoke my own g++ binary with > that parameter, it complains about unknown parameters. > > I'm perfectly happy to dig further on my own, but I get the feeling I'm > missing some documentation / resource somewhere that might help me out. > Is there some documentation about adding and passing around parameters > that will be used both in libcpp and the C++ front-end? What would be > the best place to look to learn more about how part of GCC this is > structured? I want to make sure I go about this correctly. There's a gccint.info documentation file, the Options node seems like what you're looking for. You will want to add a new option to c-family/c.opt. > If this is the wrong place to ask for help, please redirect me, so that > I don't unnecessarily spam the wrong mailing list :-). I'm not sure whether gcc@ or gcc-patches@ is better for this sort of question (without a patch). I tend to miss a lot that goes by on the mailing list, so CCing me directly about C++ changes is also helpful. Jason
Re: Implementing p0515 - spaceship operator
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 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 am very much still getting oriented. >> >> Following advice from some of the people in IRC channel I implemented >> parsing the new token in libcpp and I seem to be successfully parsing it >> and creating a new AST node. As this feature is not in the C++ standard >> yet, I wanted to add a command line flag to enable usage of the new >> operator and ignoring it otherwise. I managed to get cc1plus to accept >> the parameter, but it seems that when I invoke my own g++ binary with >> that parameter, it complains about unknown parameters. >> >> I'm perfectly happy to dig further on my own, but I get the feeling I'm >> missing some documentation / resource somewhere that might help me out. >> Is there some documentation about adding and passing around parameters >> that will be used both in libcpp and the C++ front-end? What would be >> the best place to look to learn more about how part of GCC this is >> structured? I want to make sure I go about this correctly. > > There's a gccint.info documentation file, the Options node seems like > what you're looking for. You will want to add a new option to > c-family/c.opt. operator<=> is now in the working paper though, so does it need its own option? IMHO it should just be enabled for -std=c++2a and -std=gnu++2a, and not otherwise.
Re: Implementing p0515 - spaceship operator
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++ (aka the spaceship >>> operator). >> >> Great! >> >>> 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 am very much still getting oriented. >>> >>> Following advice from some of the people in IRC channel I implemented >>> parsing the new token in libcpp and I seem to be successfully parsing it >>> and creating a new AST node. As this feature is not in the C++ standard >>> yet, I wanted to add a command line flag to enable usage of the new >>> operator and ignoring it otherwise. I managed to get cc1plus to accept >>> the parameter, but it seems that when I invoke my own g++ binary with >>> that parameter, it complains about unknown parameters. >>> >>> I'm perfectly happy to dig further on my own, but I get the feeling I'm >>> missing some documentation / resource somewhere that might help me out. >>> Is there some documentation about adding and passing around parameters >>> that will be used both in libcpp and the C++ front-end? What would be >>> the best place to look to learn more about how part of GCC this is >>> structured? I want to make sure I go about this correctly. >> >> There's a gccint.info documentation file, the Options node seems like >> what you're looking for. You will want to add a new option to >> c-family/c.opt. > > operator<=> is now in the working paper though, so does it need its > own option? IMHO it should just be enabled for -std=c++2a and > -std=gnu++2a, and not otherwise. Ah, good point. Jason
