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++/107817] std/format/functions/format.cc etc. FAIL
Date: Tue, 22 Nov 2022 17:54:46 +0000 [thread overview]
Message-ID: <bug-107817-4-BJkBbMZ9QC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107817-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107817
--- Comment #2 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:dfc1ea414e0cebccfcffc771ebcefa3d24c9754c
commit r13-4243-gdfc1ea414e0cebccfcffc771ebcefa3d24c9754c
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Nov 22 17:39:43 2022 +0000
libstdc++: Replace std::isdigit and std::isxdigit in <format> [PR107817]
These functions aren't usable in constant expressions. Provide our own
implementations, based on __from_chars_alnum_to_val from <charconv>.
libstdc++-v3/ChangeLog:
PR libstdc++/107817
* include/std/charconv (__from_chars_alnum_to_val): Add
constexpr for C++20.
* include/std/format (__is_digit, __is_xdigit): New functions.
(_Spec::_S_parse_width_or_precision): Use __is_digit.
(__formatter_fp::parse): Use __is_xdigit.
next prev parent reply other threads:[~2022-11-22 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 14:05 [Bug libstdc++/107817] New: " ro at gcc dot gnu.org
2022-11-22 14:05 ` [Bug libstdc++/107817] " ro at gcc dot gnu.org
2022-11-22 17:12 ` redi at gcc dot gnu.org
2022-11-22 17:16 ` redi at gcc dot gnu.org
2022-11-22 17:54 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-22 18:12 ` redi at gcc dot gnu.org
2022-11-22 21:35 ` redi at gcc dot gnu.org
2022-11-24 8:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-107817-4-BJkBbMZ9QC@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: link
Be 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).