From: Richard Henderson <richard.henderson@linaro.org>
To: libc-alpha@sourceware.org
Cc: adhemerval.zanella@linaro.org, goldstein.w.n@gmail.com
Subject: Re: [PATCH v8 01/17] Parameterize op_t from memcopy.h
Date: Mon, 16 Jan 2023 10:52:04 -1000 [thread overview]
Message-ID: <556ffbff-7648-7f6a-f3a0-338159f6bd60@linaro.org> (raw)
In-Reply-To: <20230113182733.1268668-2-richard.henderson@linaro.org>
On 1/13/23 08:27, Richard Henderson wrote:
> From: Adhemerval Zanella Netto<adhemerval.zanella@linaro.org>
>
> It moves the op_t definition out to an specific header, adds
> the attribute 'may-alias', and cleanup its duplicated definitions.
>
> Checked with a build and check with run-built-tests=no for all major
> Linux ABIs.
> Message-Id:<20230111204558.2402155-2-adhemerval.zanella@linaro.org>
> ---
> sysdeps/generic/memcopy.h | 6 ++----
> sysdeps/generic/string-optype.h | 24 ++++++++++++++++++++++++
> sysdeps/x86_64/x32/string-optype.h | 24 ++++++++++++++++++++++++
> string/memcmp.c | 1 -
> 4 files changed, 50 insertions(+), 5 deletions(-)
> create mode 100644 sysdeps/generic/string-optype.h
> create mode 100644 sysdeps/x86_64/x32/string-optype.h
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-01-16 20:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 18:27 [PATCH v8 00/17] Improve generic string routines Richard Henderson
2023-01-13 18:27 ` [PATCH v8 01/17] Parameterize op_t from memcopy.h Richard Henderson
2023-01-16 20:52 ` Richard Henderson [this message]
2023-01-13 18:27 ` [PATCH v8 02/17] Parameterize OP_T_THRES " Richard Henderson
2023-01-16 20:52 ` Richard Henderson
2023-01-13 18:27 ` [PATCH v8 03/17] Add string-maskoff.h generic header Richard Henderson
2023-01-16 20:58 ` Richard Henderson
2023-01-17 18:49 ` Adhemerval Zanella Netto
2023-01-18 1:33 ` Richard Henderson
2023-01-18 12:45 ` Adhemerval Zanella Netto
2023-01-13 18:27 ` [PATCH v8 04/17] Add string vectorized find and detection functions Richard Henderson
2023-01-16 21:04 ` Richard Henderson
2023-01-13 18:27 ` [PATCH v8 05/17] string: Improve generic strlen Richard Henderson
2023-01-13 18:27 ` [PATCH v8 06/17] string: Improve generic strnlen Richard Henderson
2023-01-13 18:27 ` [PATCH v8 07/17] string: Improve generic strchr Richard Henderson
2023-01-13 18:27 ` [PATCH v8 08/17] string: Improve generic strchrnul Richard Henderson
2023-01-13 18:27 ` [PATCH v8 09/17] string: Improve generic strcmp Richard Henderson
2023-01-13 18:27 ` [PATCH v8 10/17] string: Improve generic memchr Richard Henderson
2023-01-13 18:27 ` [PATCH v8 11/17] string: Improve generic memrchr Richard Henderson
2023-01-13 18:27 ` [PATCH v8 12/17] hppa: Add memcopy.h Richard Henderson
2023-01-13 18:27 ` [PATCH v8 13/17] hppa: Add string-fzb.h and string-fzi.h Richard Henderson
2023-01-13 18:27 ` [PATCH v8 14/17] alpha: " Richard Henderson
2023-01-13 18:27 ` [PATCH v8 15/17] arm: Add string-fza.h Richard Henderson
2023-01-13 18:27 ` [PATCH v8 16/17] powerpc: " Richard Henderson
2023-01-17 14:35 ` Adhemerval Zanella Netto
2023-01-13 18:27 ` [PATCH v8 17/17] sh: Add string-fzb.h Richard Henderson
2023-01-17 14:35 ` 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=556ffbff-7648-7f6a-f3a0-338159f6bd60@linaro.org \
--to=richard.henderson@linaro.org \
--cc=adhemerval.zanella@linaro.org \
--cc=goldstein.w.n@gmail.com \
--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).