diff options
author | Rich Felker <dalias@aerifal.cx> | 2013-08-01 21:44:43 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2013-08-01 21:44:43 -0400 |
commit | 926272ddffa293ee68ffeb01422fc8c792acf428 (patch) | |
tree | 8997ae7c582e5d4dbaf0056d940d15702d728258 /src/string/wcsncasecmp_l.c | |
parent | 4a1f55e92fa74ee382909baa96302231f566b5e1 (diff) | |
download | musl-926272ddffa293ee68ffeb01422fc8c792acf428.tar.gz musl-926272ddffa293ee68ffeb01422fc8c792acf428.tar.bz2 musl-926272ddffa293ee68ffeb01422fc8c792acf428.tar.xz musl-926272ddffa293ee68ffeb01422fc8c792acf428.zip |
optimized memset asm for i386 and x86_64
the concept of both versions is the same; they differ only in details.
for long runs, they use "rep movsl" or "rep movsq", and for small
runs, they use a trick, writing from both ends towards the middle,
that reduces the number of branches needed. in addition, if memset is
called multiple times with the same length, all branches will be
predicted; there are no loops.
for larger runs, there are likely faster approaches than "rep", at
least on some cpu models. for 32-bit, it's unlikely that there is any
faster approach that does not require non-baseline instructions; doing
anything fancier would require inspecting cpu capabilities. for
64-bit, there may very well be faster versions that work on all
models; further optimization could be explored in the future.
with these changes, memset is anywhere between 50% faster and 6 times
faster, depending on the cpu model and the length and alignment of the
destination buffer.
Diffstat (limited to 'src/string/wcsncasecmp_l.c')
0 files changed, 0 insertions, 0 deletions