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++/107720] [13 regression] New C++ library test cases (and many others) in r13-3936-g1d9454aba615ea fail Date: Thu, 17 Nov 2022 00:34:54 +0000 [thread overview] Message-ID: <bug-107720-4-cFeNHR7xhD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107720-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107720 --- 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:f69a8299c1d95548e1539227fb7b8f5581aeb29b commit r13-4117-gf69a8299c1d95548e1539227fb7b8f5581aeb29b Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Nov 16 20:47:39 2022 +0000 libstdc++: Ensure std::to_chars overloads all declared in <format> [PR107720] For powerpc64le we need to be able to format both of __ieee128 and __ibm128, so we need the std::to_chars overloads for both types to be visible at once. The __ieee128 overloads are always visible in C++23 mode, because they're used to implement the _Float128 overloads. The __ibm128 overloads are only visible when long double is __ibm128. libstdc++-v3/ChangeLog: PR libstdc++/107720 * include/std/format [_GLIBCXX_LONG_DOUBLE_ALT128_COMPAT]: Declare overloads of std::to_chars for the alternative long double type.
next prev parent reply other threads:[~2022-11-17 0:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 17:46 [Bug libstdc++/107720] New: " seurer at gcc dot gnu.org 2022-11-16 18:51 ` [Bug libstdc++/107720] " redi at gcc dot gnu.org 2022-11-16 20:48 ` redi at gcc dot gnu.org 2022-11-16 20:59 ` cvs-commit at gcc dot gnu.org 2022-11-17 0:34 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-17 0:35 ` 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-107720-4-cFeNHR7xhD@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).