- 30 Jul, 2014 2 commits
-
-
Matt Clarkson authored
-
Matt Clarkson authored
-
- 27 Jul, 2014 3 commits
-
-
Dominic Hamon authored
-
Dominic Hamon authored
Add Lei Xu to AUTHORS and CONTRIBUTORS
-
- 25 Jul, 2014 2 commits
- 24 Jul, 2014 2 commits
-
-
Dominic Hamon authored
fix examples to use SetBytesProcessed
-
Dominic Hamon authored
-
- 23 Jul, 2014 6 commits
-
-
Paul Redmond authored
- use State::SetBytesProcessed not SetBenchmarkBytesProcessed
-
Pierre Phaneuf authored
-
Pierre Phaneuf authored
-
Dominic Hamon authored
fix building on ubuntu
-
Paul Redmond authored
-
Paul Redmond authored
-
- 11 Jun, 2014 1 commit
-
-
Dominic Hamon authored
Fix a bug in the destruction of BenchmarkFamilies.
-
- 09 Jun, 2014 1 commit
-
-
pleroy authored
-
- 05 Jun, 2014 2 commits
-
-
Dominic Hamon authored
Take the CPU time into account in PauseTiming/ResumeTiming
-
pleroy authored
Conflicts: src/benchmark.cc
-
- 04 Jun, 2014 10 commits
-
-
Dominic Hamon authored
Fix the stddev/mean computations
-
pleroy authored
-
pleroy authored
-
pleroy authored
-
pleroy authored
-
Dominic Hamon authored
Two bug fixes in KeepRunning
-
pleroy authored
-
pleroy authored
-
Chris Kennelly authored
-
Pierre Phaneuf authored
-
- 29 May, 2014 3 commits
- 05 May, 2014 6 commits
-
-
Dominic Hamon authored
Resolve race on approx_time_ in FastClock.
-
Dominic Hamon authored
Statically initialize benchmark_mutex and extend its lifetime.
-
Dominic Hamon authored
Resolve benchmark cleanup race condition in issue #20.
-
Chris Kennelly authored
InitType should hold a lock before storing to approx_time_, which is later read by the background worker. When the worker is actively running (i.e., not blocked on bg_cond_) it holds bg_mutex_. InitType is called during benchmark setup only, so any contention induced for the mutex should not have performance/accuracy consequences.
-
Chris Kennelly authored
RunSpecifiedBenchmarks destroys benchmark_mutex before its last usage, typically in RemoveBenchmark during cleanup of the BenchmarkFamilies singleton.
-
Chris Kennelly authored
The multithreaded API for benchmarks provides that teardown can happen in thread 0. For this to be safe, all other threads executing the benchmark function need to have exited. Otherwise, thread 0 may begin to teardown shared resources before the other threads have stopped using these resources as they are in their last loop of while (KeepRunning()) { ... }. This change creates a single exit point for KeepRunning() to return false. When running a multithreaded benchmark, thread 0 blocks on KeepRunning() until all other threads have exited. This approach allows for there to be no change to the user-facing API exemplified in the BM_MultiThreaded example.
-
- 23 Apr, 2014 2 commits
-
-
Dominic Hamon authored
Remove URL_HASH and TLS_VERIFY from CMake configuration.
-
Chris Kennelly authored
Per the CMake 2.8.0 documentation, these options did not exist for ExternalProject_Add. These options were added in CMake 2.8.10.
-