From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id B459F3858C66; Sun, 28 Apr 2024 05:22:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B459F3858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714281728; bh=/JZ0MpB7g6D6rd78ubf/h4mOvI/qRm9reUeNUSh+BQ4=; h=From:To:Subject:Date:From; b=DrdyhCoJ2S6pAQA7TjLw3lMZWBrKXO2ZdgHADfO1k+Oa+ol6G0T9kBgef/XzJzYvS Nl4SFkVAkfDFKjFwlVHfCqlFGU9SYNzYonmxerQ80fD37rkVjV7aNg5UAtuSz4K7Zx OBkNKUki9aTR0U2Q690fk01beKhrtjHdX0s1d0g4= 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: b40c8c90da105a4628907dccecf571db059d86f3 X-Git-Newrev: 22b9a800e1cbf491f98a2813ef4c09463d76aaf1 Message-Id: <20240428052208.B459F3858C66@sourceware.org> Date: Sun, 28 Apr 2024 05:22:08 +0000 (GMT) List-Id: https://gcc.gnu.org/g:22b9a800e1cbf491f98a2813ef4c09463d76aaf1 commit 22b9a800e1cbf491f98a2813ef4c09463d76aaf1 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 | 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* } } */