public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Dmitry V. Levin" <ldv@strace.io>
Cc: strace development discussions <strace-devel@lists.strace.io>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v6 04/11] stdio-common: Add __translated_number_width
Date: Mon, 30 Jan 2023 11:42:21 +0100	[thread overview]
Message-ID: <87k014z4ky.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230130094055.GA12568@altlinux.org> (Dmitry V. Levin's message of "Mon, 30 Jan 2023 12:40:55 +0300")

* Dmitry V. Levin:

> Hi,
>
> On Fri, Dec 16, 2022 at 09:15:22PM +0100, Florian Weimer via Libc-alpha wrote:
>> This function will be used to compute the width of a number
>> after i18n digit translation.
>
> I haven't bisected, but I suppose it was this changeset that introduced
> a regression reported by the strace test suite.
>
> glibc-2.36$ cat <<'EOF' |gcc -xc - && ./a.out
> #include <stdio.h>
> int main() { printf("%03d\n", 1); return 0; }
> EOF
> 001
>
> The same test on master prints 0001 instead of 001.

Sorry, I can't reproduce it.  Did you build glibc yourself from upstream
sources, or did you get the build from somewhere else?

Thanks,
Florian


  reply	other threads:[~2023-01-30 10:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 20:15 [PATCH v6 00/11] vfprintf refactor Florian Weimer
2022-12-16 20:15 ` [PATCH v6 01/11] locale: Implement struct grouping_iterator Florian Weimer
2022-12-16 20:15 ` [PATCH v6 02/11] stdio-common: Introduce buffers for implementing printf Florian Weimer
2022-12-16 20:41   ` Noah Goldstein
2022-12-16 20:59     ` Florian Weimer
2022-12-16 21:14       ` Noah Goldstein
2022-12-16 22:32         ` Florian Weimer
2022-12-17  0:32           ` Noah Goldstein
2022-12-17 12:55             ` Florian Weimer
2022-12-16 20:15 ` [PATCH v6 03/11] stdio-common: Add __printf_function_invoke Florian Weimer
2022-12-16 20:15 ` [PATCH v6 04/11] stdio-common: Add __translated_number_width Florian Weimer
2023-01-30  9:40   ` Dmitry V. Levin
2023-01-30 10:42     ` Florian Weimer [this message]
2023-01-30 10:51       ` Dmitry V. Levin
2023-01-30 11:03         ` Florian Weimer
2023-01-30 11:06           ` Dmitry V. Levin
2022-12-16 20:15 ` [PATCH v6 05/11] stdio-common: Convert vfprintf and related functions to buffers Florian Weimer
2022-12-16 20:15 ` [PATCH v6 06/11] stdio-common: Add lock optimization to vfprintf and vfwprintf Florian Weimer
2022-12-16 20:15 ` [PATCH v6 07/11] libio: Convert __vsprintf_internal to buffers Florian Weimer
2022-12-16 20:15 ` [PATCH v6 08/11] libio: Convert __vasprintf_internal " Florian Weimer
2022-12-19 16:37   ` Adhemerval Zanella Netto
2022-12-16 20:15 ` [PATCH v6 09/11] libio: Convert __vdprintf_internal " Florian Weimer
2022-12-19 16:39   ` Adhemerval Zanella Netto
2022-12-16 20:15 ` [PATCH v6 10/11] libio: Convert __obstack_vprintf_internal to buffers (bug 27124) Florian Weimer
2022-12-19 17:37   ` Adhemerval Zanella Netto
2022-12-16 20:15 ` [PATCH v6 11/11] libio: Convert __vswprintf_internal to buffers (bug 27857) Florian Weimer
2022-12-19 17:53   ` Adhemerval Zanella Netto

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=87k014z4ky.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=ldv@strace.io \
    --cc=libc-alpha@sourceware.org \
    --cc=strace-devel@lists.strace.io \
    /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).