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:06:56 +0000	[thread overview]
Message-ID: <bug-99058-4-Ku95WEfA36@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 #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> C++17 support isn't stable until GCC 9 so there is no guarantee of
> compatibility between 7 and 8 or 8 and 9. That applies to the entire library
> (and language features) not just std::optional.

I should clarify that what "applies to the entire library" is the experimental
nature of C++17 features. But C++98/11/14 features like std::vector and
std::shared_ptr are compatible between GCC 7 and later releases.

  parent reply	other threads:[~2021-02-10 22:06 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 [this message]
2021-02-10 22:17 ` redi at gcc dot gnu.org
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-Ku95WEfA36@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: 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).