fanquake 52f0be3a93 compat: remove memcpy -> memmove backwards compatibility alias ... In glib 2.13 memcpy was changed such that the way it copied bytes was reversed. This caused all sorts of issues for existing software, which depended on the existing behavior (when they should have been using memmove). See: https://sourceware.org/bugzilla/show_bug.cgi?id=12518 https://bugzilla.redhat.com/show_bug.cgi?id=638477 Now that we require glibc 2.17+ (#17538), we should be well clear of having to maintain our memcpy -> memmove aliasing, which was introduced in #4339.		2021-03-10 14:31:10 +08:00
..
assumptions.h	assumptions: check C++17 assumption with MSVC	2021-02-23 12:51:50 +08:00
byteswap.h	scripted-diff: Bump copyright of files changed in 2019	2019-12-30 10:42:20 +13:00
cpuid.h	[MOVEONLY] Move cpuid code from random & sha256 to compat/cpuid	2019-11-12 14:50:44 -08:00
endian.h	Update copyright headers to 2018	2018-07-27 07:15:02 -04:00
glibc_compat.cpp	compat: remove memcpy -> memmove backwards compatibility alias	2021-03-10 14:31:10 +08:00
glibcxx_sanity.cpp	Update copyright headers to 2018	2018-07-27 07:15:02 -04:00
sanity.h	compat: remove memcpy -> memmove backwards compatibility alias	2021-03-10 14:31:10 +08:00
stdin.cpp	scripted-diff: Bump copyright of files changed in 2019	2019-12-30 10:42:20 +13:00
stdin.h	add stdin helpers for password input support	2019-10-01 12:19:31 +09:00
strnlen.cpp	Update copyright headers to 2018	2018-07-27 07:15:02 -04:00