GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th

Jeff Law law@redhat.com
Fri Nov 1 15:31:00 GMT 2019


On 11/1/19 9:08 AM, Marek Polacek wrote:
> On Fri, Nov 01, 2019 at 04:01:12PM +0100, Romain Geissler wrote:
>> Le mar. 22 oct. 2019 à 14:53, Richard Biener <rguenther@suse.de> a écrit :
>>>
>>> Please make sure to get features intended for GCC 10 finished
>>> and reviewed before the end of stage 1.
>>>
>>
>> Hi,
>>
>> I understand my question comes very (most likely too) late, but are
>> there any plans to switch the default C++ dialect to -std=gnu++17 when
>> invoking g++ ? C++17 support in gcc is now quite complete, has been
>> out tested by some users since gcc 8, so shall it be switched on by
>> default in gcc 10 ? Or gcc 11 ? However I fear doing that may break
>> some tests in the testsuite, I hope not too many.
> 
> I plan to propose a switch to -std=gnu++17 in GCC 11.  I think it's way
> too late for GCC 10.
> 
> Dealing with the testsuite fallout, and rebuilding Fedora packages is
> of course part of that switch.
FWIW, we *could* do the rebuild test, we've got time for that.  What's
far more interesting would be dealing with the fallout ;-)

I'd tend to agree though, flip the default as soon as gcc-11 stage1
opens.  That gives us plenty of time to deal with any fallout.

jeff



More information about the Gcc-patches mailing list