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 c++/110000] GCC should implement exclude_from_explicit_instantiation Date: Wed, 31 May 2023 16:52:25 +0000 [thread overview] Message-ID: <bug-110000-4-qGvcOTDyt7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110000-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110000 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #10) > Do you want to be able to change these functions in > ABI-incompatible ways between major revisions of the library? Sorry, that was unclear, I meant to ask if you want to change them in ABI-incompatible ways without bumping the version in the abi_tag? e.g. change std::__1::vector<int, std::__1::allocator<int> >::__clear[abi:v15007]() in an ABI-incompatible way, without changing the tag to [abi:v15008]? Because if the tag is going to change anyway, what does it matter if the user has instantiations of the old [abi:v15007] symbol in their lib?
next prev parent reply other threads:[~2023-05-31 16:52 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 20:25 [Bug c++/110000] New: " nikolasklauser at berlin dot de 2023-05-26 20:31 ` [Bug c++/110000] " ldionne.2 at gmail dot com 2023-05-26 20:33 ` pinskia at gcc dot gnu.org 2023-05-26 20:35 ` pinskia at gcc dot gnu.org 2023-05-26 20:42 ` nikolasklauser at berlin dot de 2023-05-27 10:39 ` fw at gcc dot gnu.org 2023-05-27 23:40 ` nikolasklauser at berlin dot de 2023-05-28 6:13 ` fw at gcc dot gnu.org 2023-05-28 14:31 ` nikolasklauser at berlin dot de 2023-05-31 15:40 ` ldionne.2 at gmail dot com 2023-05-31 16:48 ` redi at gcc dot gnu.org 2023-05-31 16:52 ` redi at gcc dot gnu.org [this message] 2023-05-31 17:33 ` nikolasklauser at berlin dot de 2023-06-01 18:00 ` ldionne.2 at gmail dot com
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-110000-4-qGvcOTDyt7@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).