public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109921] [13 Regression] c++17/floating_from_chars.cc: compile error: ‘from_chars_strtod’ was not declared in this scope
Date: Wed, 19 Jul 2023 23:33:19 +0000 [thread overview]
Message-ID: <bug-109921-4-dHhGtX6t2v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109921-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109921
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|13.3 |13.2
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This should be fixed for gcc-13 now. There should be a release candidate for
GCC 13.2 in the next day or so. If possible please download the RC tarball and
test it for your target, so that if there are still problems we can fix them
for the 13.2 release.
next prev parent reply other threads:[~2023-07-19 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 10:02 [Bug libstdc++/109921] New: " br015 at umbiko dot net
2023-05-24 11:16 ` [Bug libstdc++/109921] " redi at gcc dot gnu.org
2023-05-24 13:01 ` redi at gcc dot gnu.org
2023-05-25 8:31 ` br015 at umbiko dot net
2023-05-31 12:21 ` cvs-commit at gcc dot gnu.org
2023-05-31 12:24 ` redi at gcc dot gnu.org
2023-05-31 19:57 ` cvs-commit at gcc dot gnu.org
2023-07-19 19:53 ` redi at gcc dot gnu.org
2023-07-19 22:43 ` [Bug libstdc++/109921] [13 Regression] " cvs-commit at gcc dot gnu.org
2023-07-19 23:31 ` cvs-commit at gcc dot gnu.org
2023-07-19 23:33 ` redi at gcc dot gnu.org [this message]
2023-07-20 11:57 ` redi at gcc dot gnu.org
2023-07-21 13:04 ` redi at gcc dot gnu.org
2023-07-22 6:05 ` br015 at umbiko dot net
2023-07-22 9:01 ` 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-109921-4-dHhGtX6t2v@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).