diff options
author | Rich Felker <dalias@aerifal.cx> | 2018-11-08 15:00:02 -0500 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2018-11-08 15:22:22 -0500 |
commit | 122d67f846cb0be2c9e1c3880db9eb9545bbe38c (patch) | |
tree | a219e7810b20690c12a6ab14e47f9c57b03ac7b9 /src/thread/pthread_mutex_unlock.c | |
parent | 04e18b61dfde85e34ddea15e4a7d49f24c47bb73 (diff) | |
download | musl-122d67f846cb0be2c9e1c3880db9eb9545bbe38c.tar.gz musl-122d67f846cb0be2c9e1c3880db9eb9545bbe38c.tar.bz2 musl-122d67f846cb0be2c9e1c3880db9eb9545bbe38c.tar.xz musl-122d67f846cb0be2c9e1c3880db9eb9545bbe38c.zip |
optimize two-way strstr and memmem bad character shift
first, the condition (mem && k < p) is redundant, because mem being
nonzero implies the needle is periodic with period exactly p, in which
case any byte that appears in the needle must appear in the last p
bytes of the needle, bounding the shift (k) by p.
second, the whole point of replacing the shift k by mem (=l-p) is to
prevent shifting by less than mem when discarding the memory on shift,
in which case linear time could not be guaranteed. but as written, the
check also replaced shifts greater than mem by mem, reducing the
benefit of the shift. there is no possible benefit to this reduction of
the shift; since mem is being cleared, the full shift is valid and
more optimal. so only replace the shift by mem when it would be less
than mem.
Diffstat (limited to 'src/thread/pthread_mutex_unlock.c')
0 files changed, 0 insertions, 0 deletions