forked from dashpay/dash
-
Notifications
You must be signed in to change notification settings - Fork 716
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge #1554: [Core] Big endian support
25224a8 Replace CBlockHeader::GetHash with call to SerializeHash (random-zebra) 49a7716 Add serialize float/double tests (random-zebra) 83c6d13 src/txmempool.cpp: make numEntries a uint32_t (random-zebra) 70c6606 src/serialize.h: base serialization level endianness neutrality (random-zebra) 4ad83fe src/script/script.h: endian compatibility for PUSHDATA sizes (random-zebra) 74f1699 src/primitives/transaction.h: endian compatibility in serialization (random-zebra) b5e5de6 src/primitives/block.cpp: endian compatibility in GetHash (random-zebra) b6b4b3e src/net.cpp: endian compatibility in EndMessage (random-zebra) 1d84b73 src/netbase.h: Fix endian in CNetAddr serialization (random-zebra) 4d98939 src/main.cpp: endian compatibility in packet checksum check (random-zebra) fe2727b src/hash.cpp: endian compatibility (random-zebra) Pull request description: First step in getting our serialization code up to par with upstream. Backports bitcoin#5510 with only minor adjustments. > Fix issue bitcoin#888. > > This has been structured so that each compatibility change is one commit that touches only one file. After the initial build change, they are independent. > > Most extensive changes are in 'src/serialize.h: base serialization level endianness neutrality'. I had to replace READDATA and WRITEDATA with functions that take sized integer types to make use of the proper endian.h functions. I'm confident that the end result is the same, although this may require more tests. > > I've tested this on mipsbe32. > > All tests pass > Testnet syncs correctly > Node can successfully function on P2P mainnet Checked that data directory can be copied between endians with no adverse results (only peers.dat required special attention here) > Known issues (to be fixed before merge): > > DNS seeding always comes with 0 results on BE (confirmed as working by @paveljanik on real hardware, must have been issue with my qemu-user setup) ACKs for top commit: furszy: Everything working here, utACK 25224a8 Fuzzbawls: utACK 25224a8 Tree-SHA512: 047e3bd6a7c6bbbd341da1ec3fb7698e19d52e170ba0d475e6f451cbb52e2c55f23a15999da663a8022ddc9df3a5c168f825b779c4afb1fd210b9da680503297
- Loading branch information
Showing
10 changed files
with
280 additions
and
224 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.