nonsense benchtests results

[Paul Zimmermann]

> > thank you for your answer. I understand what I'm missing is how I can make and
> > use another trace. And where is the "workload trace for the float version"
> > located (I could not find it). I'd like to document this in benchtests/README.
> 
> grep workload benchtests/*-inputs shows the traces that have been committed.
> You can create new traces by running representative code with a printf in the
> math function you're interested in. You could also generate randomized inputs
> in an interval. They don't have to be very long, the key is to exercise a range of
> common inputs rather than repeating the same input a million times.
> 
> > PS: if traces can't have inputs that return NaN or infinity, maybe the
> > benchtests framework should check it?
> 
> Well it could be checked, but traces from real applications won't use NaN. Inf
> might happen in some math functions, but I haven't seen it in any traces so far.

thank you Wilco. I now understand how the workload traces scheme works.
After 2.32 is out, I'll submit a patch to better document that, and add
"workload" traces to a few functions.

Paul