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++/110149] std::format for pointer arguments allows a '0' option Date: Fri, 09 Jun 2023 12:09:58 +0000 [thread overview] Message-ID: <bug-110149-4-WvISZT9Ob1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110149-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110149 --- Comment #5 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:628ba410b9265dbd4278c1f1b1fadf05348adef2 commit r14-1648-g628ba410b9265dbd4278c1f1b1fadf05348adef2 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jun 8 21:35:21 2023 +0100 libstdc++: Fix P2510R3 "Formatting pointers" [PR110149] I had intended to support the P2510R3 proposal unconditionally in C++20 mode, but I left it half implemented. The parse function supported the new extensions, but the format function didn't. This adds the missing pieces, and makes it only enabled for C++26 and non-strict modes. libstdc++-v3/ChangeLog: PR libstdc++/110149 * include/std/format (formatter<const void*, charT>::parse): Only alow 0 and P for C++26 and non-strict modes. (formatter<const void*, charT>::format): Use toupper for P type, and insert zero-fill characters for 0 option. * testsuite/std/format/functions/format.cc: Check pointer formatting. Only check P2510R3 extensions conditionally. * testsuite/std/format/parse_ctx.cc: Only check P2510R3 extensions conditionally.
next prev parent reply other threads:[~2023-06-09 12:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 21:05 [Bug libstdc++/110149] New: " bruno at clisp dot org 2023-06-06 22:20 ` [Bug libstdc++/110149] " redi at gcc dot gnu.org 2023-06-06 22:46 ` redi at gcc dot gnu.org 2023-06-06 22:57 ` redi at gcc dot gnu.org 2023-06-08 12:59 ` redi at gcc dot gnu.org 2023-06-09 12:09 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-09 12:21 ` redi at gcc dot gnu.org 2023-06-29 23:01 ` cvs-commit at gcc dot gnu.org 2023-06-29 23:02 ` 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-110149-4-WvISZT9Ob1@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).