public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Marek Polacek <polacek@redhat.com>,
	Romain Geissler <romain.geissler@gmail.com>
Cc: gcc@gcc.gnu.org, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th
Date: Fri, 01 Nov 2019 15:31:00 -0000	[thread overview]
Message-ID: <e123d9fd-ba25-4a4a-ec84-826d2610ae33@redhat.com> (raw)
In-Reply-To: <20191101150835.GO21634@redhat.com>

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

  reply	other threads:[~2019-11-01 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 12:53 Richard Biener
2019-11-01 15:01 ` Romain Geissler
2019-11-01 15:08   ` Marek Polacek
2019-11-01 15:31     ` Jeff Law [this message]
2019-11-01 15:43       ` Marek Polacek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e123d9fd-ba25-4a4a-ec84-826d2610ae33@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=polacek@redhat.com \
    --cc=romain.geissler@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).