Hey,
After more thoughts, I'm wondering whether or not we should enable
benchmarks for range and strides by default. These are not informative
anyway because they depend quite a lot on the offsets used for the ranges,
and the strides used for the slices. While, on the other hand, for big
vectors,
Hey,
> I've noted that the console benchmarks for ViennaCL were quite outdated,
> performance for AXPY are reported in FLOP/s, for example. I think it'd
> be great to have something compact, all incorporated in a single
> benchmarking executable:
>
> ===
> BLAS [float, full]
>
Hey,
I've noted that the console benchmarks for ViennaCL were quite outdated,
performance for AXPY are reported in FLOP/s, for example. I think it'd be
great to have something compact, all incorporated in a single benchmarking
executable:
===
BLAS [float, full]
---
