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++/103407] [12 regression] abi_check FAILs on Solaris Date: Wed, 23 Feb 2022 15:57:25 +0000 [thread overview] Message-ID: <bug-103407-4-MSnPOQmFCy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103407-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103407 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Rainer, is an executable linked against libstdc++.so.6.0.29 on Solaris 11.3 expected to work on an 11.4 machine with libstdc++.so.6.0.30? With a #ifdef kluge in config/abi/pre/gnu.ver we can make the new from_chars symbols get version GLIBCXX_3.4.30 on 11.3 and keep them at version 3.4.29 for 11.4. But that would mean a program linked on 11.3 and looking for _ZSt10from_charsPKcS0_RdSt12chars_format@GLIBCXX_3.4.30 would not find it on 11.4. We can fix that with some symbol aliases for Solaris 11.4 to make it available for both symbol versions if needed.
next prev parent reply other threads:[~2022-02-23 15:57 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-24 11:58 [Bug libstdc++/103407] New: " ro at gcc dot gnu.org 2021-11-24 11:59 ` [Bug libstdc++/103407] " ro at gcc dot gnu.org 2021-11-24 12:05 ` rguenth at gcc dot gnu.org 2021-11-24 12:36 ` redi at gcc dot gnu.org 2021-11-25 1:05 ` pinskia at gcc dot gnu.org 2022-02-22 17:44 ` redi at gcc dot gnu.org 2022-02-23 15:57 ` redi at gcc dot gnu.org [this message] 2022-02-23 16:41 ` redi at gcc dot gnu.org 2022-02-23 16:53 ` redi at gcc dot gnu.org 2022-02-23 21:02 ` ro at gcc dot gnu.org 2022-02-24 0:58 ` redi at gcc dot gnu.org 2022-02-24 9:41 ` redi at gcc dot gnu.org 2022-02-28 14:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-10 16:16 ` redi at gcc dot gnu.org 2022-03-16 17:34 ` redi at gcc dot gnu.org 2022-03-16 21:17 ` cvs-commit at gcc dot gnu.org 2022-03-18 12:43 ` redi at gcc dot gnu.org 2022-04-29 11:50 ` cvs-commit at gcc dot gnu.org 2022-04-29 12:02 ` 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-103407-4-MSnPOQmFCy@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).