public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v5 05/11] stdio-common: Convert vfprintf and related functions to buffers
Date: Fri, 16 Dec 2022 18:58:29 +0100	[thread overview]
Message-ID: <87359ftem2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <32c237bd-1f1d-671c-71df-99005dea6746@linaro.org> (Adhemerval Zanella Netto's message of "Wed, 14 Dec 2022 17:54:29 -0300")

* Adhemerval Zanella Netto:

> Patch looks good, there is only a small nit on the libio vtable removal
> that in turn showed an issue on elf/tst-relro-symbols.py.
>
> LGTM, thanks.
>
> Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

Thanks.

>> -const struct _IO_jump_t _IO_strn_jumps libio_vtable attribute_hidden =
>
> We need to remove both _IO_strn_jumps definition from libio/strfile.h and
> from tst-relro-libc.out.

Yes, fixed.

>> -#ifdef COMPILE_WPRINTF
>> -static const struct _IO_jump_t _IO_helper_jumps libio_vtable =
>> -{

>> -#else
>> -static const struct _IO_jump_t _IO_helper_jumps libio_vtable =
>> -{

> The _IO_helper_jumps should be removed from tst-relro-symbols.py
> required list, and tst-relro-symbols.py not showing a regression
> raised some questions.  It turned out that it is not really testing
> the required symbols due a bug, with the fix below:

Right, thanks.

Florian


  reply	other threads:[~2022-12-16 17:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 15:22 [PATCH v5 00/11] vfprintf refactor Florian Weimer
2022-12-12 15:22 ` [PATCH v5 01/11] locale: Implement struct grouping_iterator Florian Weimer
2022-12-12 15:22 ` [PATCH v5 02/11] stdio-common: Introduce buffers for implementing printf Florian Weimer
2022-12-14 14:10   ` Adhemerval Zanella Netto
2022-12-16 17:51     ` Florian Weimer
2022-12-12 15:23 ` [PATCH v5 03/11] stdio-common: Add __printf_function_invoke Florian Weimer
2022-12-14 14:28   ` Adhemerval Zanella Netto
2022-12-12 15:23 ` [PATCH v5 04/11] stdio-common: Add __translated_number_width Florian Weimer
2022-12-14 14:38   ` Adhemerval Zanella Netto
2022-12-12 15:23 ` [PATCH v5 05/11] stdio-common: Convert vfprintf and related functions to buffers Florian Weimer
2022-12-14 20:54   ` Adhemerval Zanella Netto
2022-12-16 17:58     ` Florian Weimer [this message]
2022-12-12 15:23 ` [PATCH v5 06/11] stdio-common: Add lock optimization to vfprintf and vfwprintf Florian Weimer
2022-12-15 15:58   ` Adhemerval Zanella Netto
2022-12-12 15:23 ` [PATCH v5 07/11] libio: Convert __vsprintf_internal to buffers Florian Weimer
2022-12-15 18:16   ` Adhemerval Zanella Netto
2022-12-16 18:07     ` Florian Weimer
2022-12-12 15:23 ` [PATCH v5 08/11] libio: Convert __vasprintf_internal " Florian Weimer
2022-12-15 18:40   ` Adhemerval Zanella Netto
2022-12-16 18:22     ` Florian Weimer
2022-12-12 15:23 ` [PATCH v5 09/11] libio: Convert __vdprintf_internal " Florian Weimer
2022-12-15 19:11   ` Adhemerval Zanella Netto
2022-12-12 15:24 ` [PATCH v5 10/11] libio: Convert __obstack_vprintf_internal to buffers (bug 27124) Florian Weimer
2022-12-15 19:14   ` Adhemerval Zanella Netto
2022-12-16 18:25     ` Florian Weimer

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=87359ftem2.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@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).