From: dengjianbo <dengjianbo@loongson.cn>
To: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
i.swmail@xen0n.name
Cc: joseph_myers@mentor.com, carlos@redhat.com,
xuchenghua@loongson.cn, caiyinyu@loongson.cn,
dengjianbo <dengjianbo@loongson.cn>
Subject: [PATCH 0/1] LoongArch: Add optimized functions.
Date: Fri, 2 Sep 2022 16:39:07 +0800 [thread overview]
Message-ID: <20220902083908.2560918-1-dengjianbo@loongson.cn> (raw)
Tested on LoongArch machine 3A5000: gcc 12.1.0, Linux kernel 5.19.0 rc5, binutils 2.38.50, All cases are passed besides ifunc related tests, no new failed entry was introduced.
configure:
../configure --prefix=/usr CFLAGS="-O2"
make bench, comparing with the improved generic version, test results can be found in following link:
https://github.com/jiadengx/glibc/tree/main/make_bench
strchr
About 30% faster than improved generic version, detailed info can be found from strchr_xls.png and graph-strchr.
https://github.com/jiadengx/glibc/blob/main/make_bench/graph-strchr
https://github.com/jiadengx/glibc/blob/main/make_bench/strchr_xls.png
strchrnul
About 30% faster than improved generic version, detailed info can be found from strchrnul_xls.png and graph-strchrnul.
https://github.com/jiadengx/glibc/blob/main/make_bench/graph-strchrnul
https://github.com/jiadengx/glibc/blob/main/make_bench/strchrnul_xls.png
strcmp
About 10% - 60% faster than improved generic version, detailed info can be found from strcmp_xls.png and graph-strcmp.
https://github.com/jiadengx/glibc/blob/main/make_bench/graph-strcmp
https://github.com/jiadengx/glibc/blob/main/make_bench/strcmp_xls.png
strncmp
About 0% - 80% faster than generic version, detailed info can be found from strncmp_xls.png and graph-strncmp.
https://github.com/jiadengx/glibc/blob/main/make_bench/graph-strncmp
https://github.com/jiadengx/glibc/blob/main/make_bench/strncmp_xls.png
memmove
About 5% - 60% faster than improved generic version, detailed info can be found from memmove_xls.png and graph-memmove.
https://github.com/jiadengx/glibc/blob/main/make_bench/graph-memmove
https://github.com/jiadengx/glibc/blob/main/make_bench/memmove_xls.png
dengjianbo (1):
LoongArch: Add optimized functions.
sysdeps/loongarch/lp64/memmove.S | 491 +++++++++++++++++++++++++++++
sysdeps/loongarch/lp64/strchr.S | 145 +++++++++
sysdeps/loongarch/lp64/strchrnul.S | 160 ++++++++++
sysdeps/loongarch/lp64/strcmp.S | 210 ++++++++++++
sysdeps/loongarch/lp64/strncmp.S | 281 +++++++++++++++++
5 files changed, 1287 insertions(+)
create mode 100644 sysdeps/loongarch/lp64/memmove.S
create mode 100644 sysdeps/loongarch/lp64/strchr.S
create mode 100644 sysdeps/loongarch/lp64/strchrnul.S
create mode 100644 sysdeps/loongarch/lp64/strcmp.S
create mode 100644 sysdeps/loongarch/lp64/strncmp.S
--
2.20.1
next reply other threads:[~2022-09-02 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 8:39 dengjianbo [this message]
2022-09-02 8:39 ` [PATCH 1/1] " dengjianbo
2022-09-02 9:35 ` Xi Ruoyao
2022-09-02 9:52 ` Xi Ruoyao
2022-09-16 7:34 ` dengjianbo
2022-09-16 7:16 [PATCH 0/1] " dengjianbo
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=20220902083908.2560918-1-dengjianbo@loongson.cn \
--to=dengjianbo@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=carlos@redhat.com \
--cc=i.swmail@xen0n.name \
--cc=joseph_myers@mentor.com \
--cc=libc-alpha@sourceware.org \
--cc=xuchenghua@loongson.cn \
/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).