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, 16 Mar 2022 17:34:46 +0000 [thread overview] Message-ID: <bug-103407-4-BdNBoM0gbE@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 #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- I tried this instead, but I think this still counts as "binding the same symbol to different versions", and didn't work: #if defined __sun__ && defined _GLIBCXX_HAVE_USELOCALE #if defined(_GLIBCXX_SYMVER_SUN) && defined(_GLIBCXX_SHARED) \ && defined(_GLIBCXX_HAVE_AS_SYMVER_DIRECTIVE) // Solaris 11.4 supports uselocale, so std::from_chars is present since gcc-11 // with symbol version GLIBCXX_3.4.29. Solaris 11.3 does not support uselocale // so std::from_chars is not present until gcc-12, with version GLIBCXX_3.4.30. // Define aliases so that code linked on Solaris 11.3 runs on 11.4 too. from_chars_result __from_chars_compat(const char* first, const char* last, double& value, chars_format fmt) noexcept { return std::from_chars(first, last, value, fmt); } asm(".symver _ZSt19__from_chars_compatPKcS0_RdSt12chars_format, _ZSt10from_charsPKcS0_RdSt12chars_formaT@GLIBCXX_3.4.30"); from_chars_result __from_chars_compat(const char* first, const char* last, long double& value, chars_format fmt) noexcept { return std::from_chars(first, last, value, fmt); } asm(".symver _ZSt19__from_chars_compatPKcS0_ReSt12chars_format, _ZSt10from_charsPKcS0_ReSt12chars_formaT@GLIBCXX_3.4.30"); from_chars_result __from_chars_compat(const char* first, const char* last, float& value, chars_format fmt) noexcept { return std::from_chars(first, last, value, fmt); } asm(".symver _ZSt19__from_chars_compatPKcS0_RfSt12chars_format, _ZSt10from_charsPKcS0_RfSt12chars_formaT@GLIBCXX_3.4.30"); #endif #endif This does get compiled, but I don't see those @GLIBCXX_3.4.30 symbols in the DSO. Maybe I'm missing something that would make them exported as global symbols, or maybe this just can't be done on Solaris.
next prev parent reply other threads:[~2022-03-16 17:34 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 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 [this message] 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-BdNBoM0gbE@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).