Mircea Trofin 376ebc2635 Support optional, user-directed collection of performance counters (#1114) ... * Support optional, user-directed collection of performance counters The patch allows an engineer wishing to drill into the root causes of a regression, for example. Currently, only single threaded runs are supported. The feature is a build-time opt in, and then a runtime opt in. The engineer may run the benchmark executable, passing a list of performance counter names (using libpfm's naming scheme) at the command line. The counter values will then be collected and reported back as UserCounters. This is different from #240 in that it is a benchmark user opt-in, and the counter collection is transparent to the benchmark. Currently, this is only supported on platforms where libpfm is supported. libpfm: http://perfmon2.sourceforge.net/ * 'Use' values param in Snapshot when BENCHMARK_OS_WINDOWS This is to avoid unused parameter warning-as-error * Added missing include for <vector> in perf_counters.cc * Moved doc to docs * Added license blurbs		2021-04-28 09:25:29 +01:00
..
bazel.yml	Add verbosity to CI logs (#1122)	2021-04-26 18:26:33 +01:00
build-and-test-perfcounters.yml	Support optional, user-directed collection of performance counters (#1114)	2021-04-28 09:25:29 +01:00
build-and-test.yml	Add verbosity to CI logs (#1122)	2021-04-26 18:26:33 +01:00
pylint.yml	Create pylint.yml (#1039)	2020-09-09 09:43:26 +01:00
test_bindings.yml	Add workflow to exercise bindings (#1041)	2020-09-10 16:32:25 +01:00