public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/23432] incorrect printf output for integers with thousands separator and precision field larger than the number of digits (needing leading zeros)
Date: Wed, 08 Feb 2023 01:12:33 +0000 [thread overview]
Message-ID: <bug-23432-131-PyymjlbMOg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23432-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23432
--- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.37/master branch has been updated by Carlos O'Donell
<carlos@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=07b9521fc6369d000216b96562ff7c0ed32a16c4
commit 07b9521fc6369d000216b96562ff7c0ed32a16c4
Author: Carlos O'Donell <carlos@redhat.com>
Date: Thu Jan 19 12:50:20 2023 +0100
Account for grouping in printf width (bug 30068)
This is a partial fix for mishandling of grouping when formatting
integers. It properly computes the width in the presence of grouping
characters when the width is larger than the number of significant
digits. The precision related issue is documented in bug 23432.
Co-authored-by: Andreas Schwab <schwab@suse.de>
(cherry picked from commit c980549cc6a1c03c23cc2fe3e7b0fe626a0364b0)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-02-08 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23432-131@http.sourceware.org/bugzilla/>
2023-01-10 11:29 ` vincent-srcware at vinc17 dot net
2023-01-10 11:47 ` vincent-srcware at vinc17 dot net
2023-01-10 11:49 ` vincent-srcware at vinc17 dot net
2023-01-10 12:07 ` [Bug stdio/23432] incorrect printf output " vincent-srcware at vinc17 dot net
2023-01-10 12:23 ` [Bug stdio/23432] incorrect printf output for integers " vincent-srcware at vinc17 dot net
2023-01-10 12:32 ` vincent-srcware at vinc17 dot net
2023-01-17 12:15 ` schwab@linux-m68k.org
2023-01-17 12:51 ` vincent-srcware at vinc17 dot net
2023-01-17 13:32 ` schwab@linux-m68k.org
2023-02-02 1:22 ` vincent-srcware at vinc17 dot net
2023-02-06 13:58 ` vincent-srcware at vinc17 dot net
2023-02-06 15:21 ` cvs-commit at gcc dot gnu.org
2023-02-08 1:12 ` cvs-commit at gcc dot gnu.org [this message]
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-23432-131-PyymjlbMOg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).