This patch makes references in the manual to C17 reflect it having
been published in July 2018. (For the reasons it took so long to get
to ballot and publication, see the WG14 convenor's report to the last
SC22 plenary - SC22 N5297 - where it references "A troubling new trend
where ISO CS has begun enforcing undocumented rules that are approved
neither by the TMB nor by the WG 14 editors, leading to a decrease in
the usefulness of standards documents.".)
Tested with "make info html pdf". Applied to mainline.
2018-10-17 Joseph Myers <jos...@codesourcery.com>
* doc/invoke.texi (-std=c17), doc/standards.texi (C Language):
Document C17 as published in 2018.
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 265248)
+++ gcc/doc/invoke.texi (working copy)
@@ -1927,8 +1927,8 @@
@itemx c18
@itemx iso9899:2017
@itemx iso9899:2018
-ISO C17, the 2017 revision of the ISO C standard (expected to be
-published in 2018). This standard is
+ISO C17, the 2017 revision of the ISO C standard
+(published in 2018). This standard is
same as C11 except for corrections of defects (all of which are also
applied with @option{-std=c11}) and a new value of
@code{__STDC_VERSION__}, and so is supported to the same extent as C11.
Index: gcc/doc/standards.texi
===================================================================
--- gcc/doc/standards.texi (revision 265248)
+++ gcc/doc/standards.texi (working copy)
@@ -102,7 +102,8 @@
standard version were referred to as @dfn{C1X}.)
GCC has substantially complete support
for this standard, enabled with @option{-std=c11} or
-@option{-std=iso9899:2011}. A version with corrections integrated is
+@option{-std=iso9899:2011}. A version with corrections integrated was
+prepared in 2017 and published in 2018 as ISO/IEC 9899:2018; it is
known as @dfn{C17} and is supported with @option{-std=c17} or
@option{-std=iso9899:2017}; the corrections are also applied with
@option{-std=c11}, and the only difference between the options is the
--
Joseph S. Myers
jos...@codesourcery.com
