From: Carlos O'Donell <carlos@redhat.com>
To: Andreas Schwab <schwab@suse.de>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Account for grouping in printf width (bug 23432)
Date: Thu, 2 Feb 2023 08:40:51 -0500 [thread overview]
Message-ID: <ebb7ac61-1441-42ef-e70f-26bfcf758fb7@redhat.com> (raw)
In-Reply-To: <mvmpmbawxoj.fsf@suse.de>
On 1/19/23 06:50, Andreas Schwab via Libc-alpha wrote:
> This is a partial fix for mishandling of grouping when formatting
> integers. It properly computes the width in presence of grouping
> characteres when the precision is larger than the number of significant
> digits.
Thanks for working on this.
Are you working on a v2 with the $(gen-locales) dependency fix?
It would be great to get the fix Bug 30068 in release/2.37/master.
> ---
> stdio-common/Makefile | 1 +
> stdio-common/tst-grouping3.c | 37 +++++++++++++++++++++++++++++
> stdio-common/vfprintf-process-arg.c | 2 +-
> 3 files changed, 39 insertions(+), 1 deletion(-)
> create mode 100644 stdio-common/tst-grouping3.c
>
> diff --git a/stdio-common/Makefile b/stdio-common/Makefile
> index 6e9d104524..b46d932a20 100644
> --- a/stdio-common/Makefile
> +++ b/stdio-common/Makefile
> @@ -195,6 +195,7 @@ tests := \
> tst-gets \
> tst-grouping \
> tst-grouping2 \
> + tst-grouping3 \
> tst-long-dbl-fphex \
> tst-memstream-string \
> tst-obprintf \
> diff --git a/stdio-common/tst-grouping3.c b/stdio-common/tst-grouping3.c
> new file mode 100644
> index 0000000000..0031ad4010
> --- /dev/null
> +++ b/stdio-common/tst-grouping3.c
> @@ -0,0 +1,37 @@
> +/* Test printf with grouping and padding (bug 23432)
> + Copyright (C) 2023 Free Software Foundation, Inc.
> + This file is part of the GNU C Library.
> +
> + The GNU C Library is free software; you can redistribute it and/or
> + modify it under the terms of the GNU Lesser General Public
> + License as published by the Free Software Foundation; either
> + version 2.1 of the License, or (at your option) any later version.
> +
> + The GNU C Library is distributed in the hope that it will be useful,
> + but WITHOUT ANY WARRANTY; without even the implied warranty of
> + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + Lesser General Public License for more details.
> +
> + You should have received a copy of the GNU Lesser General Public
> + License along with the GNU C Library; if not, see
> + <https://www.gnu.org/licenses/>. */
> +
> +#include <locale.h>
> +#include <stdio.h>
> +#include <support/check.h>
> +#include <support/support.h>
> +
> +static int
> +do_test (void)
> +{
> + char buf[80];
> +
> + xsetlocale (LC_NUMERIC, "de_DE.UTF-8");
> +
> + sprintf (buf, "%+-'13.9d", 1234567);
> + TEST_COMPARE_STRING (buf, "+001.234.567 ");
> +
> + return 0;
> +}
> +
> +#include <support/test-driver.c>
> diff --git a/stdio-common/vfprintf-process-arg.c b/stdio-common/vfprintf-process-arg.c
> index 2c651946df..cd3eaf5c0c 100644
> --- a/stdio-common/vfprintf-process-arg.c
> +++ b/stdio-common/vfprintf-process-arg.c
> @@ -257,7 +257,7 @@ LABEL (unsigned_number): /* Unsigned number of base BASE. */
> width -= 2;
> }
>
> - width -= workend - string + prec;
> + width -= number_length + prec;
>
> Xprintf_buffer_pad (buf, L_('0'), prec);
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-02-02 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 11:50 Andreas Schwab
2023-01-21 11:40 ` Florian Weimer
2023-01-22 23:20 ` Carlos O'Donell
2023-02-02 9:51 ` Andreas Schwab
2023-02-02 10:45 ` Florian Weimer
2023-02-02 10:54 ` Andreas Schwab
2023-02-02 12:00 ` Xi Ruoyao
2023-02-02 13:10 ` Vincent Lefevre
2023-02-02 13:40 ` Carlos O'Donell [this message]
2023-02-04 16:22 ` Carlos O'Donell
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=ebb7ac61-1441-42ef-e70f-26bfcf758fb7@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).