On Sep 14, 2017, at 1:26 PM, Jakub Jelinek <ja...@redhat.com> wrote: > > Given https://herbsutter.com/2017/09/06/c17-is-formally-approved/ > this patch makes -std=c++17 and -std=gnu++17 the documented options
> --- gcc/doc/invoke.texi.jj 2017-09-12 21:57:57.000000000 +0200
> +++ gcc/doc/invoke.texi 2017-09-14 19:32:34.342959968 +0200
> @@ -1870,15 +1870,15 @@ GNU dialect of @option{-std=c++14}.
> This is the default for C++ code.
> The name @samp{gnu++1y} is deprecated.
>
> -@item c++1z
> -The next revision of the ISO C++ standard, tentatively planned for
> -2017. Support is highly experimental, and will almost certainly
> -change in incompatible ways in future releases.
> -
> -@item gnu++1z
> -GNU dialect of @option{-std=c++1z}. Support is highly experimental,
> -and will almost certainly change in incompatible ways in future
> -releases.
> +@item c++17
> +@itemx c++1z
> +The 2017 ISO C++ standard plus amendments.
> +The name @samp{c++1z} is deprecated.
> +
> +@item gnu++17
> +@itemx gnu++1z
> +GNU dialect of @option{-std=c++17}.
> +The name @samp{gnu++17} is deprecated.
I'd be tempted to say leave all this, and march 1z -> 2a for the _next_
standard. 2020 or so is a good first stab at the date.
> -or an unspecified value strictly larger than @code{201402L} for the
> -experimental languages enabled by @option{-std=c++1z} and
> -@option{-std=gnu++1z}.
> +@code{201703L} for the 2017 C++ standard.
Likewise.
Anyway, the testsuite portion is obvious and I reviewed it for correctness and
Ok.
smime.p7s
Description: S/MIME cryptographic signature
