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++/113512] New: Incorrect results for std::format("{:#.3g}", flt) Date: Fri, 19 Jan 2024 23:19:46 +0000 [thread overview] Message-ID: <bug-113512-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113512 Bug ID: 113512 Summary: Incorrect results for std::format("{:#.3g}", flt) Product: gcc Version: 13.2.1 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- std::format("{:#.3g}", 0.02) should give 3 significant figures, i.e. "0.0200" But libstdc++ counts the leading zeros as significant, so gives "0.02" std::format("{:#.3g}", 0.025) should give "0.0250" but instead throws an exception!
next reply other threads:[~2024-01-19 23:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 23:19 redi at gcc dot gnu.org [this message] 2024-01-19 23:20 ` [Bug libstdc++/113512] " redi at gcc dot gnu.org 2024-01-21 13:35 ` cvs-commit at gcc dot gnu.org 2024-01-30 14:54 ` cvs-commit at gcc dot gnu.org 2024-01-30 16:52 ` 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-113512-4@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).