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++/112832] [std::format] Broken non-SFINAE-friendly `set_debug_format()` for `const char *` formatter Date: Wed, 06 Dec 2023 14:44:42 +0000 [thread overview] Message-ID: <bug-112832-4-XCayViDZvB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:d40796e3813fdf646ca7b7ce9630d5cc121353b4 commit r13-8130-gd40796e3813fdf646ca7b7ce9630d5cc121353b4 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Dec 4 12:03:28 2023 +0000 libstdc++: Disable std::formatter::set_debug_format [PR112832] All set_debug_format member functions should be guarded by the __cpp_lib_formatting_ranges macro (which is not defined yet). libstdc++-v3/ChangeLog: PR libstdc++/112832 * include/std/format (formatter::set_debug_format): Ensure this member is defined conditionally for all specializations. * testsuite/std/format/formatter/112832.cc: New test. (cherry picked from commit 3cd73543a1122d3c81409e3e9a26c3e94c3d324f)
next prev parent reply other threads:[~2023-12-06 14:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 16:53 [Bug libstdc++/112832] New: " iamsupermouse at mail dot ru 2023-12-04 11:36 ` [Bug libstdc++/112832] " redi at gcc dot gnu.org 2023-12-05 16:49 ` cvs-commit at gcc dot gnu.org 2023-12-06 14:44 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-06 14:45 ` 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-112832-4-XCayViDZvB@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).