From: Srinivasan J <srinidpdk@gmail.com>
To: musl@lists.openwall.com
Subject: [musl] memcpy/memcmp optimizations and possible alternatives
Date: Sat, 16 May 2020 08:37:34 +0530 [thread overview]
Message-ID: <CAEbeQ+orK1naVD6+aC2=LijWsHxEL7Vmz1msorG7-=-Tv1Mj6Q@mail.gmail.com> (raw)
Hi,
I see that the musl-libc implementations of mem* functions does not
use AVX/SSE4 instructions. Please let me know if there is a plan to
support these or if there is a recommended way to use optimized
versions of mem* functions when running memory intensive applications
with musl-libc. The application is being run in alpine linux.
Thanks,
Srini
next reply other threads:[~2020-05-16 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 3:07 Srinivasan J [this message]
2020-05-16 3:40 ` Rich Felker
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='CAEbeQ+orK1naVD6+aC2=LijWsHxEL7Vmz1msorG7-=-Tv1Mj6Q@mail.gmail.com' \
--to=srinidpdk@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).