[LLVMdev] YA Vectorization Benchmark

[Daniel Dunbar]

Seems fairly reasonable to me.

I don't know what size of arrays you are dealing with, if they are
reasonably small it is probably also fine to just output each element in
the result.

It's fine to start by just setting FP_TOLERANCE to a small value and if it
breaks in the future because of an actual precision change we can tweak it.

Thanks for the reformatting, its great to see new benchmarks getting added!

 - Daniel



On Fri, Nov 16, 2012 at 12:28 PM, Renato Golin <rengolin at systemcall.org>wrote:

> Daniel, Nadav, Hal,
>
> So, after some painstakingly boring re-formatting, I've split the 24
> kernels into 24 files (and left a horrible header file with code in
> it, which I'll clean up later).
>
> Since we're taking times in the benchmark tool, and we're trying to
> assert the quality of the FP approximation by the vectorization, I'll
> try to come up with a reasonable watermark for each test. Maybe adding
> the values of all elements in the result vector, or something, and
> printing that value, using FP_TOLERANCE to detect errors in the
> vectorized code.
>
> Does this seem sensible?
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121116/6e9bc5d9/attachment.html>