diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gcc.target/spu/dfcgt-nan.c | |
download | cbb-gcc-4.6.4-upstream.tar.bz2 cbb-gcc-4.6.4-upstream.tar.xz |
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.
downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.
if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.
Diffstat (limited to 'gcc/testsuite/gcc.target/spu/dfcgt-nan.c')
-rw-r--r-- | gcc/testsuite/gcc.target/spu/dfcgt-nan.c | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/gcc/testsuite/gcc.target/spu/dfcgt-nan.c b/gcc/testsuite/gcc.target/spu/dfcgt-nan.c new file mode 100644 index 000000000..18ce01356 --- /dev/null +++ b/gcc/testsuite/gcc.target/spu/dfcgt-nan.c @@ -0,0 +1,31 @@ +/* { dg-do compile } */ +/* { dg-options "-march=celledp -O1" } */ +/* { dg-final { scan-assembler "dfceq" } } */ + +/* GCC previously transformed an "a <= b" test into "! (a > b)" when + compiling with -march=celledp, so that the dfcgt instruction can be + used to implement the comparison. + + However, this transformation violates the IEEE-754 standard in the + presence of NaN values. If either a or b is a NaN, a <= b should + evaluate to false according to IEEE rules. However, after the + transformation, a > b as implemented by dfcgt itself returns false, + so the transformed test returns true. + + Note that the equivalent transformation is valid for single- + precision floating-point values on the Cell SPU, because the format + does not have NaNs. It is invalid for double-precision, even on + Cell, however. */ + +int test (double a, double b) __attribute__ ((noinline)); +int test (double a, double b) +{ + return a <= b; +} + +int main (void) +{ + double x = 0.0; + double y = 0.0/0.0; + return test (x, y); +} |