public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 2330b0f89b6ac47cbb2253562a350eb1d121dd69
Date: Mon, 31 Aug 2020 20:31:16 +0000 (GMT)	[thread overview]
Message-ID: <20200831203116.D08D83857C76@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  2330b0f89b6ac47cbb2253562a350eb1d121dd69 (commit)
      from  ba10ec5f1d50e740abba71fbaae0211ff2229e41 (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 2330b0f89b6ac47cbb2253562a350eb1d121dd69
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon Aug 31 16:30:51 2020 -0400

    cxx-status: Use C++20 instead of C++2a.

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index d942e7d3..e69decdb 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -18,7 +18,7 @@
     <li><a href="#cxx11">C++11</a></li>
     <li><a href="#cxx14">C++14</a></li>
     <li><a href="#cxx17">C++17</a></li>
-    <li><a href="#cxx2a">C++2a</a></li>
+    <li><a href="#cxx20">C++20</a></li>
     <li><a href="#tses">Technical Specifications</a></li>
   </ul>
   
@@ -31,27 +31,27 @@
    Implementation Status</a> section of the Libstdc++ manual.
   </p>
 
-  <h2 id="cxx2a">C++2a Support in GCC</h2>
+  <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>C++2a features are available since GCC 8. To enable C++2a
+  <p>C++20 features are available since GCC 8. To enable C++20
       support, add the command-line parameter <code>-std=c++20</code>
       (use <code>-std=c++2a</code> in GCC 9 and earlier)
       to your <code>g++</code> command line. Or, to enable GNU
-      extensions in addition to C++2a features,
-    add <code>-std=gnu++2a</code>.</p>
+      extensions in addition to C++20 features,
+    add <code>-std=gnu++20</code>.</p>
 
-  <p><strong>Important</strong>: Because the ISO C++2a standard is
+  <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++2a features that do not reflect the final standard.</p>
+  C++20 features that do not reflect the final standard.</p>
 
-  <h2>C++2a Language Features</h2>
+  <h2>C++20 Language Features</h2>
 
   <p>The following table lists new language features that have been
-  accepted into the C++2a working draft. The "Proposal" column
+  accepted into the C++20 working draft. The "Proposal" column
   provides a link to the ISO C++ committee proposal that describes the
   feature, while the "Available in GCC?" column indicates the first
   version of GCC that contains an implementation of this feature (if

-----------------------------------------------------------------------

Summary of changes:
 htdocs/projects/cxx-status.html | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-08-31 20:31 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=20200831203116.D08D83857C76@sourceware.org \
    --to=mpolacek@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: 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).