mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-01-28 03:57:31 -03:00
52f0be3a93
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.
21 lines
691 B
C++
21 lines
691 B
C++
// Copyright (c) 2012-2020 The Bitcoin Core developers
|
|
// Distributed under the MIT software license, see the accompanying
|
|
// file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
|
|
|
#include <compat/sanity.h>
|
|
#include <key.h>
|
|
#include <test/util/setup_common.h>
|
|
#include <util/time.h>
|
|
|
|
#include <boost/test/unit_test.hpp>
|
|
|
|
BOOST_FIXTURE_TEST_SUITE(sanity_tests, BasicTestingSetup)
|
|
|
|
BOOST_AUTO_TEST_CASE(basic_sanity)
|
|
{
|
|
BOOST_CHECK_MESSAGE(glibcxx_sanity_test() == true, "stdlib sanity test");
|
|
BOOST_CHECK_MESSAGE(ECC_InitSanityCheck() == true, "secp256k1 sanity test");
|
|
BOOST_CHECK_MESSAGE(ChronoSanityCheck() == true, "chrono epoch test");
|
|
}
|
|
|
|
BOOST_AUTO_TEST_SUITE_END()
|