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++/114692] [14 Regression] Symbol versioning problem in GCC 14 libstdc++.so.6
Date: Thu, 11 Apr 2024 11:27:58 +0000	[thread overview]
Message-ID: <bug-114692-4-3aUhgKcpzF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114692-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114692

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
--- a/libstdc++-v3/config/abi/pre/gnu.ver
+++ b/libstdc++-v3/config/abi/pre/gnu.ver
@@ -2521,9 +2521,12 @@ GLIBCXX_3.4.31 {
 GLIBCXX_3.4.32 {
     _ZSt21ios_base_library_initv;
    
_ZNSt7__cxx1112basic_stringI[cw]St11char_traitsI[cw]ESaI[cw]EE11_S_allocateERS3_[jmy];
+} GLIBCXX_3.4.31;
+
+GLIBCXX_3.4.33 {
     # std::basic_file<>::native_handle()
     _ZNKSt12__basic_fileI[cw]E13native_handleEv;
-} GLIBCXX_3.4.31;
+} GLIBCXX_3.4.32;

 # Symbols in the support library (libsupc++) have their own tag.
 CXXABI_1.3 {

  parent reply	other threads:[~2024-04-11 11:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 11:20 [Bug libstdc++/114692] New: " jakub at gcc dot gnu.org
2024-04-11 11:20 ` [Bug libstdc++/114692] " jakub at gcc dot gnu.org
2024-04-11 11:22 ` redi at gcc dot gnu.org
2024-04-11 11:27 ` redi at gcc dot gnu.org [this message]
2024-04-11 11:28 ` jakub at gcc dot gnu.org
2024-04-11 11:29 ` jakub at gcc dot gnu.org
2024-04-11 11:31 ` redi at gcc dot gnu.org
2024-04-11 11:31 ` redi at gcc dot gnu.org
2024-04-11 11:34 ` redi at gcc dot gnu.org
2024-04-11 11:37 ` jakub at gcc dot gnu.org
2024-04-11 11:46 ` jakub at gcc dot gnu.org
2024-04-11 13:52 ` redi at gcc dot gnu.org
2024-04-11 14:24 ` cvs-commit at gcc dot gnu.org
2024-04-11 14:24 ` redi at gcc dot gnu.org
2024-05-07 12:46 ` cvs-commit at gcc dot gnu.org
2024-05-14  9:50 ` cvs-commit 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-114692-4-3aUhgKcpzF@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).