llvm dev - May 2012 - [LLVMdev] Adding Polybench to the test suite

Hi all,

We are trying to add Polybench[1] to the LLVM test suite. So far we
have all but five benchmarks working fine. The problems we're having
in those five benchmarks are due to gcc's versus clang's different
ways to output 'Nan's. We are working to solve this.

Although the patch is not ready yet to be included in the LLVM test
suite, we would like to have some feedback from the LLVM comunity to
know if we need to change anything else. I've removed the problematic
benchmarks from the Makefiles for now, so you should be able to run
all of the benchmarks, and all of them should pass the tests.


[1] http://www.cse.ohio-state.edu/~pouchet/software/polybench/

Cheers,

Douglas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Polybench.zip
Type: application/zip
Size: 110061 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20120530/861a40f1/attachment.zip>

Hi Douglas,
> We are trying to add Polybench[1] to the LLVM test suite. So far we
> have all but five benchmarks working fine. The problems we're having
> in those five benchmarks are due to gcc's versus clang's different
> ways to output 'Nan's. We are working to solve this.
is it normal (i.e. valid) that they output NaN's differently, or is it a
bug?

Ciao, Duncan.

Hi Duncan,

On Wed, May 30, 2012 at 4:28 PM, Duncan Sands <baldrick at free.fr>
wrote:
> Hi Douglas,
>
>> We are trying to add Polybench[1] to the LLVM test suite. So far we
>> have all but five benchmarks working fine. The problems we're
having
>> in those five benchmarks are due to gcc's versus clang's
different
>> ways to output 'Nan's. We are working to solve this.
>
> is it normal (i.e. valid) that they output NaN's differently, or is it
a
> bug?
>
We get basically the same output with clang and gcc. The only
difference is that we get a lot of '-nan's using gcc and we get
'nan's
using clang. Tobias sent me this earlier today:
"An implementation may give zero and values that are not
floating-point numbers (such as  infinities and NaNs) a sign or may
leave them unsigned. Wherever such values are   unsigned, any
requirement in this International Standard to retrieve the sign shall
produce  an unspecified sign, and any requirement to set the sign
shall be ignored."

So I don't think it is bug, but we're getting different results, anyway.

Cheers,

Douglas
> Ciao, Duncan.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev