search for: benchmark_min_tim

...or millions of > invocations for small functions... > Google benchmarks executes the kernel at max 1e9 times or until CPU time is greater than the minimum time or the wallclock time is 5x minimum time, by default min time is 0.5s but we can change it using "MinTime(X)" or "--benchmark_min_time=X". So the stabilization of small/fine grained kernel with google benchmark should not be any problem. > > > > On May 29, 2018, at 2:06 PM, Michael Kruse via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Thanks for your remarks. > > > >...

Not going into all the detail, but from my side the big question is whether the benchmarks inner loop is small/fine grained enough that stabilization with google benchmark doesn't lead to dozens of seconds benchmark runtimes. Given that you typically see thousandsd or millions of invocations for small functions... > On May 29, 2018, at 2:06 PM, Michael Kruse via llvm-dev <llvm-dev at