vetter/shoc

on Windows, QTC timing results are nonsense

Closed this issue · 1 comments

On a GTX460, I got various infinity runtimes. On a Quadro FX 380, I got results like 1e-207 seconds and e+192 seconds.

It turns out the way the timing code worked, it was adding wall clock times to uninitialized values. I guess on Windows, uninitialized really means uninitialized; otherwise, we should have noticed this before now.

I initialized the runtime values to 0.