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] [14 Regression] Symbol versioning problem in GCC 14 libstdc++.so.6
Date: Thu, 11 Apr 2024 11:46:59 +0000	[thread overview]
Message-ID: <bug-114692-4-dPlbNAIQ9f@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 #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #7)
> (In reply to Jonathan Wakely from comment #4)
> > This were added by r13-7320-g0d5a359140503d which is in 13.2 :-(
> 
> Oops, guess too late then for those.  We'll need to consider 13.2 as a fuzzy
> snapshot in between 13.1 and 13.3 then

GCC 13.1 was April 26th and didn't contain any GLIBCXX_3.4.32 I think;
then I've committed r13-7287 on April 28th, which added
_ZSt21ios_base_library_initv,
that was intentionally in a symver shared both by 13.2 and 14.1
then you've committed r13-7320 backport which added those 2 _S_allocate symbols
(with 3 size_t variants); and then 13.2 released on July 27th
So, the only bug is the _ZNKSt12__basic_fileI[cw]E13native_handleEv;
Though, surprisingly, the gnu.ver side says both Ic and Iw, while the
baseline_symbols.txt updates clearly indicate that only the Ic version is
exported.

  parent reply	other threads:[~2024-04-11 11:47 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
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 [this message]
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-dPlbNAIQ9f@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).