From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id B1F9A3858C52; Sun, 21 Apr 2024 20:27:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B1F9A3858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1713731255; bh=GTiDHerWOwZ2htt82gV/RjovHwtSY+iwnrRhGTGJQMY=; h=From:To:Subject:Date:From; b=ef5mZ79yp4lnhq1bWhHw69TVkz2jm/Rx8RX8sE9A/+velL0L3EfLVSRPteLC6fjsf kEkSiJBWkV0xfMKJNVOOVxGkDJqwJBxhd/8Of5ABNX5P6oTBvoFC0vV0AE/+YZCm76 HHpgwuva7GJfVJAjX2SEaaMxAIGsmcBNO85jrHA4= 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: 4488f8d930768029f3ca3b18709a2652462bd7c5 X-Git-Newrev: 0e8ef1e608028e5812900b717406d1901d98d4cf Message-Id: <20240421202735.B1F9A3858C52@sourceware.org> Date: Sun, 21 Apr 2024 20:27:35 +0000 (GMT) List-Id: https://gcc.gnu.org/g:0e8ef1e608028e5812900b717406d1901d98d4cf commit 0e8ef1e608028e5812900b717406d1901d98d4cf Author: Alexandre Oliva 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* } } */