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++/110653] Support std::stoi etc. without C99 APIs Date: Wed, 19 Jul 2023 10:04:27 +0000 [thread overview] Message-ID: <bug-110653-4-Z5SO5yzvOx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110653-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653 --- Comment #14 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:f0b0c21152b337bc9a8ef3a72a15c8dcdff1d847 commit r14-2636-gf0b0c21152b337bc9a8ef3a72a15c8dcdff1d847 Author: Jonathan Wakely <jwakely@redhat.com> Date: Sat Jul 15 20:41:28 2023 +0100 libstdc++: Define std::stof fallback in terms of std::stod [PR110653] For targets without std::strtof we can define std::stof by calling std::stod and then checking if the result is out of range of float. libstdc++-v3/ChangeLog: PR libstdc++/110653 * include/bits/basic_string.h [!_GLIBCXX_HAVE_STRTOF] (stof): Define in terms of std::stod.
next prev parent reply other threads:[~2023-07-19 10:04 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-13 9:40 [Bug libstdc++/110653] New: " redi at gcc dot gnu.org 2023-07-13 9:43 ` [Bug libstdc++/110653] " redi at gcc dot gnu.org 2023-07-13 13:46 ` redi at gcc dot gnu.org 2023-07-13 15:14 ` dave.anglin at bell dot net 2023-07-13 16:59 ` cvs-commit at gcc dot gnu.org 2023-07-13 17:09 ` redi at gcc dot gnu.org 2023-07-13 17:57 ` dave.anglin at bell dot net 2023-07-13 18:16 ` dave.anglin at bell dot net 2023-07-14 1:20 ` dave.anglin at bell dot net 2023-07-14 7:39 ` redi at gcc dot gnu.org 2023-07-14 9:58 ` redi at gcc dot gnu.org 2023-07-15 14:52 ` dave.anglin at bell dot net 2023-07-15 19:39 ` redi at gcc dot gnu.org 2023-07-19 10:04 ` cvs-commit at gcc dot gnu.org 2023-07-19 10:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-19 10:04 ` cvs-commit at gcc dot gnu.org 2023-07-19 10:10 ` redi at gcc dot gnu.org 2023-07-19 10:10 ` redi at gcc dot gnu.org 2023-07-19 13:48 ` dave.anglin at bell dot net 2023-07-19 13:51 ` redi at gcc dot gnu.org 2023-07-21 18:25 ` dave.anglin at bell dot net 2023-07-21 18:27 ` redi at gcc dot gnu.org 2023-07-24 20:04 ` cvs-commit at gcc dot gnu.org 2023-08-10 19:25 ` danglin 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-110653-4-Z5SO5yzvOx@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).