slackcoder/bitcoin - Bitcoin Code integration/staging tree

Age	Commit message (Collapse)	Author
2016-05-27	bench: Added base58 encoding/decoding benchmarks	Yuri Zhykin

2016-05-11	bench: Add crypto hash benchmarks	Wladimir J. van der Laan
	Add benchmarks for the cryptographic hash algorithms: - RIPEMD160 - SHA1 - SHA256 - SHA512 Continues work on #7883.
2016-04-28	Benchmark rolling bloom filter	Pieter Wuille

2016-02-04	Merge #7349: Build against system UniValue when available	Wladimir J. van der Laan
	42407ed build-unix: Update UniValue build conditions (Luke Dashjr) cdcad9f LDADD dependency order shuffling (Luke Dashjr) 62f7f2e Bugfix: Always include univalue in DIST_SUBDIRS (Luke Dashjr) 2356515 Change default configure option --with-system-univalue to "no" (Luke Dashjr) 5d3b29b doc: Add UniValue to build instructions (Luke Dashjr) ab22705 Build against system UniValue when available (Luke Dashjr) 2adf7e2 Bugfix: The var is LIBUNIVALUE,not LIBBITCOIN_UNIVALUE (Luke Dashjr)
2016-01-31	LDADD dependency order shuffling	Luke Dashjr

2016-01-15	Bugfix: The var is LIBUNIVALUE,not LIBBITCOIN_UNIVALUE	Luke Dashjr

2015-12-08	Build: Consensus: Move consensus files from common to its own module/package	Jorge Timón

2015-11-09	build: Split hardening/fPIE options out	Cory Fields
	This allows for fPIE to be used selectively.
2015-09-30	Support very-fast-running benchmarks	Gavin Andresen
	Avoid calling gettimeofday every time through the benchmarking loop, by keeping track of how long each loop takes and doubling the number of iterations done between time checks when they take less than 1/16'th of the total elapsed time.
2015-09-30	Simple benchmarking framework	Gavin Andresen
	Benchmarking framework, loosely based on google's micro-benchmarking library (https://github.com/google/benchmark) Wny not use the Google Benchmark framework? Because adding Even More Dependencies isn't worth it. If we get a dozen or three benchmarks and need nanosecond-accurate timings of threaded code then switching to the full-blown Google Benchmark library should be considered. The benchmark framework is hard-coded to run each benchmark for one wall-clock second, and then spits out .csv-format timing information to stdout. It is left as an exercise for later (or maybe never) to add command-line arguments to specify which benchmark(s) to run, how long to run them for, how to format results, etc etc etc. Again, see the Google Benchmark framework for where that might end up. See src/bench/MilliSleep.cpp for a sanity-test benchmark that just benchmarks 'sleep 100 milliseconds.' To compile and run benchmarks: cd src; make bench Sample output: Benchmark,count,min,max,average Sleep100ms,10,0.101854,0.105059,0.103881