[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:2062c8d2122c4b7dc82af9a7114136ca371da5ff

commit 2062c8d2122c4b7dc82af9a7114136ca371da5ff
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:11 2024 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f188faa3ccf 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,5 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
+/* The ppc xfail is because of PR target/58684.  */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:22b9a800e1cbf491f98a2813ef4c09463d76aaf1

commit 22b9a800e1cbf491f98a2813ef4c09463d76aaf1
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:11 2024 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..4574342e728 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,5 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
+/* remove the xfail for powerpc when pr58684 is fixed */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:1dd110cf0d45a2716102a53cc42f809e29d909ae

commit 1dd110cf0d45a2716102a53cc42f809e29d909ae
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:11 2024 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f188faa3ccf 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,5 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
+/* The ppc xfail is because of PR target/58684.  */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:f605eecb06d40c99be2d48169c5fafda2df6babb

commit f605eecb06d40c99be2d48169c5fafda2df6babb
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:11 2024 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:0e8ef1e608028e5812900b717406d1901d98d4cf

commit 0e8ef1e608028e5812900b717406d1901d98d4cf
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:11 2024 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:8c132e57c0b8951d69d7da57996ca9e200e52974

commit 8c132e57c0b8951d69d7da57996ca9e200e52974
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Apr 5 11:26:32 2023 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:0fce6126aaf4b31557dfaf1f5cfaf8c06dc1bab8

commit 0fce6126aaf4b31557dfaf1f5cfaf8c06dc1bab8
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 30 05:06:26 2023 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:53ecd201e8a9297c05620c763e815714f52a43b7

commit 53ecd201e8a9297c05620c763e815714f52a43b7
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 23 00:44:17 2023 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:80cf564d372b64aea00affad62738d08f1a773e7

commit 80cf564d372b64aea00affad62738d08f1a773e7
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 23 00:44:17 2023 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:2fcc21cb448e0889cdd9ee4285d1c58755e85a9b

commit 2fcc21cb448e0889cdd9ee4285d1c58755e85a9b
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 18 05:35:19 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:01709b16efdbf46496f2110ad2f414fca25813c3

commit 01709b16efdbf46496f2110ad2f414fca25813c3
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 18 05:35:19 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:d8c720fbe0fd7d206dbb7ba5af1c13d5c15dfc77

commit d8c720fbe0fd7d206dbb7ba5af1c13d5c15dfc77
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue Mar 9 18:42:57 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/58684
            * gcc.dg/torture/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:0b0c6d23861901ad1d79c896a08d8efd36ad6ec9

commit 0b0c6d23861901ad1d79c896a08d8efd36ad6ec9
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue Mar 9 18:42:57 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/testsuite/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:b395eb6412ebdd6ae266bd295e4f3648a1134c8b

commit b395eb6412ebdd6ae266bd295e4f3648a1134c8b
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Mar 8 23:22:46 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/testsuite/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */

[gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu

[Alexandre Oliva]

https://gcc.gnu.org/g:fbc4f186ee81edb22ad9d8143e868b966ef0e143

commit fbc4f186ee81edb22ad9d8143e868b966ef0e143
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Mar 8 23:22:46 2021 -0300

    xfail fetestexcept test - ppc always uses fcmpu
    
    gcc.dg/torture/pr91323.c tests that a compare with NaNf doesn't set an
    exception using builtin compare intrinsics, and that it does when
    using regular compare operators.
    
    That doesn't seem to be expected to work on powerpc targets.  It fails
    on GNU/Linux, it's marked to be skipped on AIX, and a similar test,
    gcc.dg/torture/pr93133.c, has the execution test xfailed for all of
    powerpc*-*-*.
    
    In this test, the functions that use intrinsics for the compare end up
    with the same code as the one that uses compare operators, using
    fcmpu, a floating compare that, unlike fcmpo, does not set the invalid
    operand exception for quiet NaN.  I couldn't find any evidence that
    the rs6000 backend ever outputs fcmpo.  Therefore, I'm adding the same
    execution xfail marker to this test.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/testsuite/pr91323.c: Expect execution fail on
            powerpc*-*-*.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr91323.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr91323.c b/gcc/testsuite/gcc.dg/torture/pr91323.c
index 1411fcaa396..f97dcc12cac 100644
--- a/gcc/testsuite/gcc.dg/torture/pr91323.c
+++ b/gcc/testsuite/gcc.dg/torture/pr91323.c
@@ -1,4 +1,4 @@
-/* { dg-do run } */
+/* { dg-do run { xfail powerpc*-*-* } } */
 /* { dg-add-options ieee } */
 /* { dg-require-effective-target fenv_exceptions } */
 /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */