Benchmark suite...

[Jeroen Dobbelaere]

Hi,

Michael Meissner wrote:
> 
[..]
> cache nowadays).  Also when I was using the benchmark suite 9+ years ago to
> tune the 88k compiler, I found that the system clock (which for the 88k was 100
> times a second) was too coarse grained to be of any use -- one clock tick
> more/less would seriously upset the timing.

Have a look at bench++ (like Klaus-Georg Adams suggested) :
(< http://www.research.att.com/~orost/bench_plus_plus.html >)

it contains timing code to adapt automagically to the speed of your system.

A test in this benchmark consists normally of a
function containing the code to be optimized, and a function
containing 'hand optimized code' to check how effective the optimizer has been.

If you keep the 'hand optimized code' empty, you will measure how many times/second
you can execute your test without the calling overhead.
The test engine adapts itself to the timing granularity of your system
and runs until a certain accuracy has been reached.

Hope this helps,

Greetings,

Jeroen Dobbelaere