[LLVMdev] YA Vectorization Benchmark

Renato Golin rengolin at systemcall.org
Fri Nov 16 12:28:32 PST 2012


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



More information about the llvm-dev mailing list