From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Paul Eggert <eggert@cs.ucla.edu>,
Noah Goldstein <goldstein.w.n@gmail.com>,
Sunil K Pandey <skpgkp2@gmail.com>
Cc: libc-alpha@sourceware.org, hjl.tools@gmail.com
Subject: Re: [PATCH] x86_64: Implement AVX2 version of strlcpy/wcslcpy function
Date: Mon, 3 Jul 2023 09:55:11 -0300 [thread overview]
Message-ID: <d27db38e-1c10-6a14-b39a-73700b78a967@linaro.org> (raw)
In-Reply-To: <eef664ab-ce82-b4b5-0dba-76e235cd8ab8@cs.ucla.edu>
On 30/06/23 18:27, Paul Eggert wrote:
> On 2023-06-30 14:04, Noah Goldstein via Libc-alpha wrote:
>> Think we should at the very least wait for the generic strlcpy codes
>> to land first.
>
> Let's not optimize these functions at all, unless there's good and measured reason to do so. In practice I expected they're called with small sizes for which optimization is a net minus as it consumes valuable maintenance time with no real benefit.
I tend to agree, although these are now added in next POSIX my understanding
is there are still not encouraged to be used due multiple shortcoming on
previous discussion.
next prev parent reply other threads:[~2023-07-03 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 20:48 Sunil K Pandey
2023-06-30 21:04 ` Noah Goldstein
2023-06-30 21:27 ` Paul Eggert
2023-06-30 22:21 ` Sunil Pandey
2023-06-30 23:22 ` Noah Goldstein
2023-06-30 23:27 ` Noah Goldstein
2023-07-03 16:30 ` Paul Eggert
2023-07-03 18:40 ` Noah Goldstein
2023-07-03 18:54 ` Adhemerval Zanella Netto
2023-07-03 21:14 ` Paul Eggert
2023-07-03 22:04 ` Gabriel Ravier
2023-07-03 23:12 ` Paul Eggert
2023-07-04 7:45 ` Andreas Schwab
2023-07-03 12:55 ` Adhemerval Zanella Netto [this message]
2023-07-01 9:41 ` Florian Weimer
2023-07-02 1:22 ` Noah Goldstein
2023-07-02 6:51 ` Florian Weimer
2023-07-02 16:55 ` Noah Goldstein
2023-07-02 17:02 ` Florian Weimer
2023-07-02 17:03 ` Noah Goldstein
2023-07-02 18:37 ` Sunil Pandey
2023-07-02 18:54 ` Noah Goldstein
2023-07-03 1:03 ` Sunil Pandey
2023-07-03 1:47 ` Noah Goldstein
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=d27db38e-1c10-6a14-b39a-73700b78a967@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=eggert@cs.ucla.edu \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@gmail.com \
/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).