public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r9-9357] libstdc++: Document when C++11/14/17 support became stable [PR 99058]
Date: Mon, 19 Apr 2021 09:05:15 +0000 (GMT) [thread overview]
Message-ID: <20210419090515.C9DCD39450F1@sourceware.org> (raw)
https://gcc.gnu.org/g:2ede3f69d27e082cbba69b77e9807b06e3ad1730
commit r9-9357-g2ede3f69d27e082cbba69b77e9807b06e3ad1730
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Feb 11 15:35:23 2021 +0000
libstdc++: Document when C++11/14/17 support became stable [PR 99058]
libstdc++-v3/ChangeLog:
PR libstdc++/99058
* doc/xml/manual/status_cxx2011.xml: Document when support
became stable.
* doc/xml/manual/status_cxx2014.xml: Likewise.
* doc/xml/manual/status_cxx2017.xml: Likewise.
* doc/html/manual/status.html: Regenerate.
(cherry picked from commit ce43c906049b828c0472d8499b52ac6233c869d0)
Diff:
---
libstdc++-v3/doc/html/manual/status.html | 9 +++++++++
libstdc++-v3/doc/xml/manual/status_cxx2011.xml | 3 +++
libstdc++-v3/doc/xml/manual/status_cxx2014.xml | 3 +++
libstdc++-v3/doc/xml/manual/status_cxx2017.xml | 3 +++
4 files changed, 18 insertions(+)
diff --git a/libstdc++-v3/doc/html/manual/status.html b/libstdc++-v3/doc/html/manual/status.html
index 26793d9fa83..e303f570e87 100644
--- a/libstdc++-v3/doc/html/manual/status.html
+++ b/libstdc++-v3/doc/html/manual/status.html
@@ -153,6 +153,9 @@ features. See <a class="link" href="using.html#manual.intro.using.flags" title="
options. The pre-defined symbol
<code class="constant">__cplusplus</code> is used to check for the
presence of the required flag.
+GCC 5.1 was the first release with non-experimental C++11 support,
+so the API and ABI of features added in C++11 is only stable
+since that release.
</p><p>
This status table is based on the table of contents of ISO/IEC 14882:2011.
</p><p>
@@ -387,6 +390,9 @@ features. See <a class="link" href="using.html#manual.intro.using.flags" title="
options. The pre-defined symbol
<code class="constant">__cplusplus</code> is used to check for the
presence of the required flag.
+GCC 6.1 was the first release with non-experimental C++14 support,
+so the API and ABI of features added in C++14 is only stable
+since that release.
</p><p>
This status table is based on the table of contents of ISO/IEC 14882:2014.
Some subclauses are not shown in the table where the content is unchanged
@@ -514,6 +520,9 @@ features. See <a class="link" href="using.html#manual.intro.using.flags" title="
options. The pre-defined symbol
<code class="constant">__cplusplus</code> is used to check for the
presence of the required flag.
+GCC 9.1 was the first release with non-experimental C++17 support,
+so the API and ABI of features added in C++17 is only stable
+since that release.
</p><p>
This section describes the C++17 and library TS support in the GCC 9 series.
</p><p>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
index 431eb02bb6b..e737232d48d 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
@@ -24,6 +24,9 @@ features. See <link linkend="manual.intro.using.flags">dialect</link>
options. The pre-defined symbol
<constant>__cplusplus</constant> is used to check for the
presence of the required flag.
+GCC 5.1 was the first release with non-experimental C++11 support,
+so the API and ABI of features added in C++11 is only stable
+since that release.
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
index f0872f6f8d0..156e0120250 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
@@ -17,6 +17,9 @@ features. See <link linkend="manual.intro.using.flags">dialect</link>
options. The pre-defined symbol
<constant>__cplusplus</constant> is used to check for the
presence of the required flag.
+GCC 6.1 was the first release with non-experimental C++14 support,
+so the API and ABI of features added in C++14 is only stable
+since that release.
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 898b029e66b..2910021a899 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -17,6 +17,9 @@ features. See <link linkend="manual.intro.using.flags">dialect</link>
options. The pre-defined symbol
<constant>__cplusplus</constant> is used to check for the
presence of the required flag.
+GCC 9.1 was the first release with non-experimental C++17 support,
+so the API and ABI of features added in C++17 is only stable
+since that release.
</para>
<para>
reply other threads:[~2021-04-19 9:05 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=20210419090515.C9DCD39450F1@sourceware.org \
--to=redi@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-cvs@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).