public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Noah Goldstein via Libc-alpha <libc-alpha@sourceware.org>
Cc: Sunil K Pandey <skpgkp2@gmail.com>,
	 Noah Goldstein <goldstein.w.n@gmail.com>,
	 hjl.tools@gmail.com
Subject: Re: [PATCH] x86_64: Implement AVX2 version of strlcpy/wcslcpy function
Date: Sat, 01 Jul 2023 11:41:21 +0200	[thread overview]
Message-ID: <87mt0gvuim.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAFUsyfKxMOO10mnzi1tK__RHxg86ohe-qwxSN2_iK7iriOPceg@mail.gmail.com> (Noah Goldstein via Libc-alpha's message of "Fri, 30 Jun 2023 16:04:38 -0500")

* Noah Goldstein via Libc-alpha:

> Think we should at the very least wait for the generic strlcpy codes
> to land first.

Do you mean a version of string/strlcpy.c that is based on a modified
string/stplcpy.c, rather than the one we have now that calls just strlen
and memcpy?

Thanks,
Florian


  parent reply	other threads:[~2023-07-01  9:41 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
2023-07-01  9:41   ` Florian Weimer [this message]
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=87mt0gvuim.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --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).