From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id 5D7BC384842D; Fri, 24 Mar 2023 06:24:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D7BC384842D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679639056; bh=JNdAd5gTSJB8K+MYKfMaFBMNvTYZQbkxP7VLNvyiUxA=; h=From:To:Subject:Date:From; b=k2Pv/1xC/xOjLnAeX6kb3E5WL70pDlm44M8zrdHOaqoeQ7Q6Ii9a3O8dd0JQuSahu ERVS0oya2g2pSQOs4Lxp9xUcCRm+3pmYHPT2S1Wr90tCx+EwUIC32bToc9LJgDCtuE QC602kVcuhw+f33jinNlT1/ga/oAojT9HVfMNP2w= 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: 25b9448a83d36a3a4ec1ae5d3cbfe60e8436e2ef X-Git-Newrev: 53ecd201e8a9297c05620c763e815714f52a43b7 Message-Id: <20230324062416.5D7BC384842D@sourceware.org> Date: Fri, 24 Mar 2023 06:24:16 +0000 (GMT) List-Id: https://gcc.gnu.org/g:53ecd201e8a9297c05620c763e815714f52a43b7 commit 53ecd201e8a9297c05620c763e815714f52a43b7 Author: Alexandre Oliva 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* } } */