public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f7f141c798d86c9ff2506d816fae4955035eba40 Date: Tue, 5 Jan 2021 21:46:26 +0000 (GMT) [thread overview] Message-ID: <20210105214626.D844C388E817@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via f7f141c798d86c9ff2506d816fae4955035eba40 (commit) from 3bafc24ce613d08fa84c8fbd20abad142e7b825e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit f7f141c798d86c9ff2506d816fae4955035eba40 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jan 5 22:46:05 2021 +0100 Adjust for the official release of ISO 14882:2020. diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index 07c560ce..9caa34eb 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -33,8 +33,8 @@ <h2 id="cxx20">C++20 Support in GCC</h2> - <p>GCC has experimental support for the next revision of the C++ - standard, which is expected to be published in 2020.</p> + <p>GCC has experimental support for the latest revision of the C++ + standard, which was published in 2020.</p> <p>C++20 features are available since GCC 8. To enable C++20 support, add the command-line parameter <code>-std=c++20</code> @@ -44,9 +44,7 @@ add <code>-std=gnu++20</code>.</p> <p><strong>Important</strong>: Because the ISO C++20 standard is - still evolving, GCC's support is <strong>experimental</strong>. No attempt - will be made to maintain backward compatibility with implementations of - C++20 features that do not reflect the final standard.</p> + very recent, GCC's support is <strong>experimental</strong>.</p> <h2>C++20 Language Features</h2> @@ -597,7 +595,7 @@ <h2 id="cxx17">C++17 Support in GCC</h2> - <p>GCC has almost full support for the latest revision of the C++ + <p>GCC has almost full support for the previous revision of the C++ standard, which was published in 2017. Some library features are missing or incomplete, as described in <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017">the library documentation</a>. @@ -924,8 +922,7 @@ <h2 id="cxx14">C++14 Support in GCC</h2> - <p>GCC has full support for the previous revision of the C++ - standard, which was published in 2014.</p> + <p>GCC has full support for the of the 2014 C++ standard.</p> <p>This mode is the default in GCC 6.1 up until GCC 10 (including); it can be explicitly selected with the <code>-std=c++14</code> command-line flag, ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cxx-status.html | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-01-05 21:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210105214626.D844C388E817@sourceware.org \ --to=jakub@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /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: linkBe 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).