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++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc Date: Fri, 06 Jan 2023 13:25:45 +0000 [thread overview] Message-ID: <bug-108221-4-RdYJKCweqI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108221-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #4 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:8c330fd49464f3d47a7c171d767eb3a011add76b commit r13-5047-g8c330fd49464f3d47a7c171d767eb3a011add76b Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jan 5 14:04:32 2023 +0000 libstdc++: Disable broken std::format for floating-point types [PR108221] If we don't have std::to_chars for floating-point types (either because float and double are not IEEE format, or size_t is 16-bit) then we can't use them with std::format. This causes a bootstrap failure since std/c++20/tzdb.cc was added to the library, because <chrono> now includes <format>. This change just disables formatting support for those types. This is not a proper fix, but solves the bootstrap failure for now. libstdc++-v3/ChangeLog: PR libstdc++/108221 * include/std/format (basic_format_arg) [!__cpp_lib_to_chars]: Disable visiting floating-point types.
next prev parent reply other threads:[~2023-01-06 13:25 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-25 9:58 [Bug libstdc++/108221] New: " jdx at o2 dot pl 2022-12-27 9:55 ` [Bug libstdc++/108221] " marxin at gcc dot gnu.org 2023-01-05 0:55 ` redi at gcc dot gnu.org 2023-01-05 12:23 ` redi at gcc dot gnu.org 2023-01-05 14:02 ` redi at gcc dot gnu.org 2023-01-06 13:25 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-06 13:27 ` redi at gcc dot gnu.org 2023-01-07 1:09 ` jdx at o2 dot pl 2023-01-07 1:13 ` redi at gcc dot gnu.org 2023-01-07 1:17 ` redi at gcc dot gnu.org 2023-01-07 1:23 ` redi at gcc dot gnu.org 2023-01-07 1:25 ` redi at gcc dot gnu.org 2023-01-07 8:29 ` jdx at o2 dot pl 2023-01-07 10:34 ` redi at gcc dot gnu.org 2023-01-08 11:44 ` jdx at o2 dot pl 2023-01-09 12:58 ` redi at gcc dot gnu.org 2023-01-10 10:10 ` cvs-commit at gcc dot gnu.org 2023-01-10 10:10 ` cvs-commit at gcc dot gnu.org 2023-01-10 11:48 ` redi at gcc dot gnu.org 2023-01-12 4:32 ` jdx at o2 dot pl 2023-01-13 17:04 ` jdx at o2 dot pl 2023-01-13 17:40 ` redi at gcc dot gnu.org 2023-01-30 18:00 ` jdx at o2 dot pl 2023-01-30 19:28 ` redi at gcc dot gnu.org 2023-01-31 16:26 ` 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-108221-4-RdYJKCweqI@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).