Liubov Dmitrieva c044cf14b0 Fix wrong copying processing for last bytes in x86-32 wcscpy ... Wrong copy algorithm for last bytes, not thread safety. In some particular cases it uses the destination memory beyond the string end for 16-byte load, puts changes into that part that is relevant to destination string and writes whole 16-byte chunk into memory. I have a test case where the memory beyond the string end contains malloc/free data, that appear corrupted in case free() updates it in between the 16-byte read and 16-byte write.		2011-12-23 08:50:39 -05:00
..
fpu	No need for boundary case handling in x86-32 __ieee_log	2011-10-15 22:21:53 -04:00
multiarch	Fix wrong copying processing for last bytes in x86-32 wcscpy	2011-12-23 08:50:39 -05:00
add_n.S
bcopy.S
bzero.S
cacheinfo.c	32bit memset-sse2.S fails with uneven cache size	2010-11-05 07:57:46 -04:00
dl-hash.h
ffs.c
hp-timing.c
hp-timing.h
Implies
Makefile	Pass -mtune=i686 to assembler when compiling for i686	2010-03-04 21:30:17 -08:00
memcmp.S
memcpy_chk.S
memcpy.S
memmove_chk.S
memmove.S
mempcpy_chk.S
mempcpy.S
memset_chk.S
memset.S
memusage.h
strcmp.S
strtok_r.S
strtok.S
tst-stack-align.h