From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: "Érico Nogueira" <ericonr@disroot.org>, libc-alpha@sourceware.org
Subject: Re: [RFC v2] linux: use __fd_to_filename helper function instead of snprintf.
Date: Mon, 3 May 2021 17:47:57 -0300 [thread overview]
Message-ID: <f50ac897-e846-a237-390f-c8bc2defb732@linaro.org> (raw)
In-Reply-To: <CB3W5BVDNFV2.TITAY65RFUTG@mussels>
On 03/05/2021 17:26, Érico Nogueira wrote:
> On Mon May 3, 2021 at 4:26 PM -03, Adhemerval Zanella wrote:
>>
>>
>> On 27/04/2021 10:09, Érico Nogueira via Libc-alpha wrote:
>>> Change made to fchmodat and fexecve. There are tests using xasprintf
>>> instead of this helper as well, but this commit doesn't touch them.
>>
>> To adapt the tests it would require either to build it as
>> internal/static
>> or add fd_to_filename to libsupport. I am not this is really an
>> improvement.
>
> That might explain some of the build failures I got when I tried
> changing the tests.
>
>>
>> LGTM, thanks. I will commit this for you.
>
> Thanks!
>
> I found a few more places where __fd_to_filename could be used, they are
> currently using _fitoa_word together with stpcpy. Would you be
> interested in making __fd_to_filename use _fitoa_word or _itoa_word? Or
> should it be left as is?
I think it might worth to check whether making __fd_to_filename use
_itoa_word yield any code size gain, but in general it seems a good
refactor.
prev parent reply other threads:[~2021-05-03 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 13:09 [RFC v2] linux: use __fd_to_filename helper function instead of snprintf Érico Nogueira via Libc-alpha
2021-05-03 19:26 ` Adhemerval Zanella via Libc-alpha
2021-05-03 20:26 ` Érico Nogueira via Libc-alpha
2021-05-03 20:47 ` Adhemerval Zanella via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f50ac897-e846-a237-390f-c8bc2defb732@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=ericonr@disroot.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).