public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99058] Consider adding a note about std::optional ABI break to the C++17 status table Date: Wed, 10 Feb 2021 22:17:57 +0000 [thread overview] Message-ID: <bug-99058-4-EeoAfWZh44@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99058-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99058 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- I think the following doc patch would probably help. --- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml +++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml @@ -24,6 +24,8 @@ 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 C++11 components is only stable from that release on. </para> <para> diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml index 61bea5adad5..af4bb6dc736 100644 --- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml +++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml @@ -17,6 +17,8 @@ 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 C++14 components is only stable from that release on. </para> <para> diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml index aa34b8c3cf5..a3c23ba54e8 100644 --- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml +++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml @@ -17,6 +17,8 @@ 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 C++17 components is only stable from that release on. </para> <para>
next prev parent reply other threads:[~2021-02-10 22:17 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-10 13:07 [Bug libstdc++/99058] New: " bspencer at blackberry dot com 2021-02-10 18:49 ` [Bug libstdc++/99058] " redi at gcc dot gnu.org 2021-02-10 18:49 ` redi at gcc dot gnu.org 2021-02-10 19:44 ` bspencer at blackberry dot com 2021-02-10 21:58 ` redi at gcc dot gnu.org 2021-02-10 22:06 ` redi at gcc dot gnu.org 2021-02-10 22:17 ` redi at gcc dot gnu.org [this message] 2021-02-10 22:19 ` redi at gcc dot gnu.org 2021-02-11 13:45 ` bspencer at blackberry dot com 2021-02-11 17:28 ` cvs-commit at gcc dot gnu.org 2021-02-12 14:49 ` redi at gcc dot gnu.org 2021-03-29 20:02 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:05 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:08 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:08 ` redi at gcc dot gnu.org
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=bug-99058-4-EeoAfWZh44@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).