diff options
author | fanquake <fanquake@gmail.com> | 2021-03-10 14:31:10 +0800 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2021-03-10 14:31:10 +0800 |
commit | 52f0be3a933225429b9b59b58de4fe54c2b20a02 (patch) | |
tree | 845655cb778ae48044cb06bc4f3d92e7d994cc0c /src/compat/sanity.h | |
parent | bca5ee6f38f0ac89f0bb90d9e005b5bbd7c25b82 (diff) |
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.
Diffstat (limited to 'src/compat/sanity.h')
-rw-r--r-- | src/compat/sanity.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/compat/sanity.h b/src/compat/sanity.h index 909c4f6da8..8efa416102 100644 --- a/src/compat/sanity.h +++ b/src/compat/sanity.h @@ -5,7 +5,6 @@ #ifndef BITCOIN_COMPAT_SANITY_H #define BITCOIN_COMPAT_SANITY_H -bool glibc_sanity_test(); bool glibcxx_sanity_test(); #endif // BITCOIN_COMPAT_SANITY_H |