[PATCH] Add sinf and cosf traces
Wilco Dijkstra
Wilco.Dijkstra@arm.com
Fri Dec 14 22:36:00 GMT 2018
Hi Carlos,
I'll see whether the description could be improved. However the specific details
don't matter all that much - the most important thing is to ensure a real trace is
used when optimizing code since repeating the same input in a loop does not give
useful results at all. Periodic functions using range reduction must have inputs
which exercise the various code paths.
When replaying the traces I noticed there are very distinct usage patterns across
the range which showed large variations in throughput/latency. So that's why
there are 3 separate scenarios representing those cases. These traces can't
capture the full behaviour of real workloads of course, however they are
representative enough that faster execution of the traces also speeds up any
application which uses sin/cos/sincos. And that's what matters.
Cheers,
Wilco
More information about the Libc-alpha
mailing list