From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 44350 invoked by alias); 1 Nov 2019 15:31:18 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 44341 invoked by uid 89); 1 Nov 2019 15:31:18 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy= X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-1.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Nov 2019 15:31:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1572622275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:openpgp:openpgp:autocrypt:autocrypt; bh=sz0I9berOvydS9jB+R1IxIIyU2IEJnQjo/Crm/HsJQ4=; b=fN7UbDZ8LrpPjq6O8bB20htNcdZQzL25lqnJ/I9B0jj9z74jnKSKVpj89xe7X53pKQOenY +IeoU+zqZIA97qOuPUmu+4Oo9e8cFD7D2fxzxCXEOEyoZj+2+Rv+ukPsEBB1WE/nWsHDKv IRTPi1T7rDagkUZ4PN847mjZibfmYJs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-63-m0KBl-10PRKBUQP6kBrcxg-1; Fri, 01 Nov 2019 11:31:13 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D92BE2EE2; Fri, 1 Nov 2019 15:31:12 +0000 (UTC) Received: from localhost.localdomain (ovpn-112-3.rdu2.redhat.com [10.10.112.3]) by smtp.corp.redhat.com (Postfix) with ESMTP id 196301001281; Fri, 1 Nov 2019 15:31:08 +0000 (UTC) Subject: Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th To: Marek Polacek , Romain Geissler Cc: gcc@gcc.gnu.org, GCC Patches References: <20191101150835.GO21634@redhat.com> From: Jeff Law Openpgp: preference=signencrypt Message-ID: Date: Fri, 01 Nov 2019 15:31:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20191101150835.GO21634@redhat.com> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00006.txt.bz2 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 =C3=A0 14:53, Richard Biener a = =C3=A9crit : >>> >>> 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=3Dgnu++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. >=20 > I plan to propose a switch to -std=3Dgnu++17 in GCC 11. I think it's way > too late for GCC 10. >=20 > 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