public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100146] __cpp_lib_to_chars not defined
Date: Mon, 19 Apr 2021 09:58:52 +0000 [thread overview]
Message-ID: <bug-100146-4-gBN2hevQAM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100146-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100146
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |ppalka at gcc dot gnu.org,
| |redi at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-04-19
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
charconv-// FIXME: Define when floating point is supported:
charconv:// #define __cpp_lib_to_chars 201611L
version:// #define __cpp_lib_to_chars 201611L
since r10-1020-gcd0b94e650a880b2ab04922e476aa28007277d5c (with adjustments).
But in
https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017
P0067R5 support is marked as completed.
next prev parent reply other threads:[~2021-04-19 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 9:42 [Bug libstdc++/100146] New: " gcc-bugs at marehr dot dialup.fu-berlin.de
2021-04-19 9:58 ` jakub at gcc dot gnu.org [this message]
2021-04-19 10:24 ` [Bug libstdc++/100146] " jakub at gcc dot gnu.org
2021-04-19 10:36 ` redi at gcc dot gnu.org
2021-04-19 11:01 ` jakub at gcc dot gnu.org
2021-04-19 11:15 ` redi at gcc dot gnu.org
2021-04-19 11:19 ` redi at gcc dot gnu.org
2021-04-20 11:51 ` cvs-commit at gcc dot gnu.org
2021-04-20 11:54 ` cvs-commit at gcc dot gnu.org
2021-04-20 11:55 ` redi at gcc dot gnu.org
2021-04-20 12:01 ` gcc-bugs at marehr dot dialup.fu-berlin.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-100146-4-gBN2hevQAM@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).