aboutsummaryrefslogtreecommitdiff
path: root/src/Makefile.leveldb.include
AgeCommit message (Collapse)Author
2020-05-12build: Enable -Wsuggest-overrideHennadii Stepanov
2020-05-03build: warn on potentially uninitialized readsVasil Dimov
Enable -Wconditional-uninitialized to warn on potentially uninitialized reads. Fix the sole such warning in Bitcoin Core in GetRdRand(): r1 would be set to 0 on rdrand failure, so initializing it to 0 is a non-functional change. From "Intel 64 and IA-32 ArchitecturesSoftware Developer's Manual" [1], page 1711: "CF=1 indicates that the data in the destination is valid. Otherwise CF=0 and the data in the destination operand will be returned as zeros for the specified width." [1] https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf
2020-01-28build: CRC32C build system integrationWladimir J. van der Laan
2020-01-28build: Update build system for new leveldbWladimir J. van der Laan
Upstream leveldb switched build systems, which means we need to define a few different values.
2019-01-26build: Remove WINVER pre define in Makefile.leveldb.inlcudeChun Kuan Lee
2017-07-13build: verify that the assembler can handle crc32 functionsCory Fields
Also, enable crc32 even if -msse4.2 wasn't added by us, as long as it works. This allows custom flags (such as -march=native) to work as expected.
2017-06-09Add extra LevelDB source to MakefileMarcoFalke
2017-06-09leveldb: enable runtime-detected crc32 instructionsCory Fields
2016-09-29Merge #8826: Do not include env_win.cc on non-Windows systemsWladimir J. van der Laan
7e5fd71 Do not include env_win.cc on non-Windows systems (Pavel Janík)
2016-09-28Do not include env_win.cc on non-Windows systemsPavel Janík
2016-09-21Add MIT license to MakefilesLuke Dashjr
2016-06-01build: out-of-tree fixupsCory Fields
Don't glob the leveldb for dist. That means we need to enumerate the headers.
2016-04-30build: No need to check for leveldb atomicsCory Fields
They're guaranteed with c++11
2016-04-19leveldb: integrate leveldb into our buildsystemCory Fields
leveldb's buildsystem causes us a few problems: - breaks out-of-tree builds - forces flags used for some tools - limits cross builds Rather than continuing to add wrappers around it, simply integrate it into our build.