public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris Date: Fri, 09 Jun 2023 12:26:00 +0000 [thread overview] Message-ID: <bug-110077-4-uu1lLfe9UH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110077-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:00da6bcfccbc5ab13821d8dd7334dd48c22d5702 commit r14-1651-g00da6bcfccbc5ab13821d8dd7334dd48c22d5702 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Jun 9 11:08:03 2023 +0100 libstdc++: Remove duplicate definition of _Float128 std::from_chars [PR110077] When long double uses IEEE binary128 representation we define the _Float128 overload of std::from_chars inline in <charconv>. My changes in r14-1431-g7037e7b6e4ac41 cause it to also be defined non-inline in the library, leading to an abi-check failure for (at least) sparc and aarch64. Suppress the definition in the library if long double and _Float128 have are both IEEE binary128. libstdc++-v3/ChangeLog: PR libstdc++/110077 * src/c++17/floating_from_chars.cc (from_chars) <_Float128>: Only define if _Float128 and long double have different representations.
next prev parent reply other threads:[~2023-06-09 12:26 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 10:57 [Bug libstdc++/110077] New: " ro at gcc dot gnu.org 2023-06-01 10:57 ` [Bug libstdc++/110077] " ro at gcc dot gnu.org 2023-06-01 10:58 ` redi at gcc dot gnu.org 2023-06-01 11:00 ` redi at gcc dot gnu.org 2023-06-09 10:17 ` redi at gcc dot gnu.org 2023-06-09 12:26 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-09 12:26 ` redi at gcc dot gnu.org 2023-06-12 11:26 ` ro at gcc dot gnu.org 2023-06-29 12:46 ` redi at gcc dot gnu.org 2023-06-29 12:54 ` ro at gcc dot gnu.org 2023-06-29 12:55 ` ro at gcc dot gnu.org 2023-06-29 13:33 ` redi at gcc dot gnu.org 2023-06-29 14:41 ` redi at gcc dot gnu.org 2023-06-29 14:42 ` redi at gcc dot gnu.org 2023-06-29 14:52 ` redi at gcc dot gnu.org 2023-06-30 13:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-06-30 14:47 ` redi at gcc dot gnu.org 2023-07-19 20:14 ` redi at gcc dot gnu.org 2023-07-19 22:43 ` cvs-commit at gcc dot gnu.org 2023-07-19 22:45 ` redi at gcc dot gnu.org 2023-07-21 11:35 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-07-21 13:04 ` redi 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-110077-4-uu1lLfe9UH@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).