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++/105324] std::from_chars() assertion at floating_from_chars.cc:78 when parsing 1.11111111.... Date: Fri, 06 May 2022 10:34:34 +0000 [thread overview] Message-ID: <bug-105324-4-jEN1JjFG80@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105324 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:799ff8e3e38f62632a98f8931ca291d191e677d5 commit r11-9960-g799ff8e3e38f62632a98f8931ca291d191e677d5 Author: Alexandre Oliva <oliva@adacore.com> Date: Fri May 6 07:33:50 2022 -0300 [PR105324] libstdc++: testsuite: pr105324 requires FP from_char The floating-point overloads of from_char are only declared if _GLIBCXX_HAVE_USELOCALE is #defined as nonzero. That's exposed from charconv as __cpp_lib_to_chars >= 201611L, so guard the test body with that. for libstdc++-v3/ChangeLog PR c++/105324 * testsuite/20_util/from_chars/pr105324.cc: Guard test body with conditional for floating-point overloads of from_char. (cherry picked from commit 25389f3de489c25a6983db96428a6bf06aedc829)
next prev parent reply other threads:[~2022-05-06 10:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 1:40 [Bug c++/105324] New: " nishida_kenji at nintendo dot co.jp 2022-04-21 9:24 ` [Bug c++/105324] " redi at gcc dot gnu.org 2022-04-21 10:34 ` cvs-commit at gcc dot gnu.org 2022-04-21 12:34 ` cvs-commit at gcc dot gnu.org 2022-04-21 12:38 ` redi at gcc dot gnu.org 2022-05-02 21:43 ` aoliva at gcc dot gnu.org 2022-05-02 21:53 ` redi at gcc dot gnu.org 2022-05-03 17:58 ` [Bug libstdc++/105324] " cvs-commit at gcc dot gnu.org 2022-05-06 10:27 ` cvs-commit at gcc dot gnu.org 2022-05-06 10:34 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-06 10:37 ` [Bug c++/105324] " aoliva 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-105324-4-jEN1JjFG80@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).