mirror of
https://github.com/google/benchmark.git
synced 2024-11-29 18:34:47 +00:00
80a62618e8
Much like it makes sense to enumerate all the families, it makes sense to enumerate stuff within families. Alternatively, we could have a global instance index, but i'm not sure why that would be better. This will be useful when the benchmarks are run not in order, for the tools to sort the results properly.
47 lines
1.7 KiB
C++
47 lines
1.7 KiB
C++
#include <memory>
|
|
|
|
#include "../src/check.h"
|
|
#include "benchmark/benchmark.h"
|
|
#include "output_test.h"
|
|
|
|
class TestMemoryManager : public benchmark::MemoryManager {
|
|
void Start() BENCHMARK_OVERRIDE {}
|
|
void Stop(Result* result) BENCHMARK_OVERRIDE {
|
|
result->num_allocs = 42;
|
|
result->max_bytes_used = 42000;
|
|
}
|
|
};
|
|
|
|
void BM_empty(benchmark::State& state) {
|
|
for (auto _ : state) {
|
|
benchmark::DoNotOptimize(state.iterations());
|
|
}
|
|
}
|
|
BENCHMARK(BM_empty);
|
|
|
|
ADD_CASES(TC_ConsoleOut, {{"^BM_empty %console_report$"}});
|
|
ADD_CASES(TC_JSONOut, {{"\"name\": \"BM_empty\",$"},
|
|
{"\"family_index\": 0,$", MR_Next},
|
|
{"\"per_family_instance_index\": 0,$", MR_Next},
|
|
{"\"run_name\": \"BM_empty\",$", MR_Next},
|
|
{"\"run_type\": \"iteration\",$", MR_Next},
|
|
{"\"repetitions\": 1,$", MR_Next},
|
|
{"\"repetition_index\": 0,$", MR_Next},
|
|
{"\"threads\": 1,$", MR_Next},
|
|
{"\"iterations\": %int,$", MR_Next},
|
|
{"\"real_time\": %float,$", MR_Next},
|
|
{"\"cpu_time\": %float,$", MR_Next},
|
|
{"\"time_unit\": \"ns\",$", MR_Next},
|
|
{"\"allocs_per_iter\": %float,$", MR_Next},
|
|
{"\"max_bytes_used\": 42000$", MR_Next},
|
|
{"}", MR_Next}});
|
|
ADD_CASES(TC_CSVOut, {{"^\"BM_empty\",%csv_report$"}});
|
|
|
|
int main(int argc, char* argv[]) {
|
|
std::unique_ptr<benchmark::MemoryManager> mm(new TestMemoryManager());
|
|
|
|
benchmark::RegisterMemoryManager(mm.get());
|
|
RunOutputTests(argc, argv);
|
|
benchmark::RegisterMemoryManager(nullptr);
|
|
}
|