RE: Choosing the timer to use in benchmarking

It was a bit random across the different suites. CoreMark uses clock_gettime(CLOCK_REALTIME, ...) which is a wall clock with NTP adjustments. EEMBC uses clock() which is a lower resolution wall clock.

So everything was mostly wall clock based. We had not tested CLOCK_PROCESS_CPUTIME_ID internally and people were happily surprised of functionality/accuracy of your results. I assume this clock is just requiring a hrtimer + stats accumulation per process/thread in scheduler but I clearly prefer it to be there rather than post-processing a scheduler trace !

Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920