clock() time travel.

Thu Jan 16 14:21:00 GMT 2014

On 16/01/14 11:54, PaweÅ‚ Sikora wrote:
> Hi,
>
> i've observed on my i3-540 cpu that subsequent clock() calls 
> *sometimes* give smaller number of ticks than previous one.
> is it a known issue?
>
> BR,
> PaweÅ‚.
How many cpus do you have?
Maybe you get a lower result than provided previously when it was 
running on a different core/cpu?
Can you also print the cpu which is giving you each answer?