From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id 68F18385843D; Thu, 16 Mar 2023 14:21:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 68F18385843D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678976501; bh=WWbBODuiX3aV+8hkicKgfUz1xeqqLLODltH+msvIzjM=; h=From:To:Subject:Date:From; b=NDovVh5CVWo19wgyHK39aXMbQJXf968hevbxmtwopSiVThXb6qkOSpskZloSA3Afd Vx/ZprKEcmcI7ia5o6867mL8QH6n8pDH5A9jtfglaSTNsJ7sVjJ9+q+cUr6Hdocc4Z hgofdGGhp+QB9SEyhM2kvrbKd4/TP1hlIh3O5hHQ= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexandre Oliva To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu X-Act-Checkin: gcc X-Git-Author: Alexandre Oliva X-Git-Refname: refs/users/aoliva/heads/testme X-Git-Oldrev: 9957e5804f693d82cb4948b06816f6e7cc451995 X-Git-Newrev: 2fcc21cb448e0889cdd9ee4285d1c58755e85a9b Message-Id: <20230316142141.68F18385843D@sourceware.org> Date: Thu, 16 Mar 2023 14:21:41 +0000 (GMT) List-Id: https://gcc.gnu.org/g:2fcc21cb448e0889cdd9ee4285d1c58755e85a9b commit 2fcc21cb448e0889cdd9ee4285d1c58755e85a9b Author: Alexandre Oliva 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* } } */