public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114692] New: [14 Regression] Symbol versioning problem in GCC 14 libstdc++.so.6 Date: Thu, 11 Apr 2024 11:20:21 +0000 [thread overview] Message-ID: <bug-114692-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114692 Bug ID: 114692 Summary: [14 Regression] Symbol versioning problem in GCC 14 libstdc++.so.6 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- I was just updating libstdc++ baseline_symbols.txt files from latest Fedora, but seems we have a major issue. While the CXXABI_1.3.15 symver is really new in GCC 14 and got one symbol, I think GCC 13.1 shipped with GLIBCXX_3.4.31 as latest symver, but then we applied PR108969 fix for 13.2 and added one symbol to GLIBCXX_3.4.32 - _ZSt21ios_base_library_initv. But new symbols for GCC 14 should have been therefore added to GLIBCXX_3.4.33, but they were actually added to GLIBCXX_3.4.32 which already shipped in GCC 13.2: _ZNKSt12__basic_fileIcE13native_handleEv@@GLIBCXX_3.4.32 _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE11_S_allocateERS3_m@@GLIBCXX_3.4.32 _ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE11_S_allocateERS3_m@@GLIBCXX_3.4.32 (or s/m@/j@/ or s/m@/y@/).
next reply other threads:[~2024-04-11 11:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 11:20 jakub at gcc dot gnu.org [this message] 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 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@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).