From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id 0CDD23858298; Wed, 15 Mar 2023 14:04:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CDD23858298 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678889093; bh=sC3e2gf2KRLZe02gg9tPH06Q9OzN3nDgNJgdpaNIEa4=; h=From:To:Subject:Date:From; b=HxhCaKEzUESeLArC8uy8vO6a4wATCocZLroMRt2E9whunjjY/ubdHX9xBdrTO73nX VqaNVaywk6NgGKE2g7IPFnM/0uDDWQK7TdbVWgjxVuoTkrxmXe7cZMISI7beGO3mAE lVk4IQkp+QGdR5r9XAxXaesNYJeDAYd4sqTA/0/o= 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: dc4b841d223d5c54da58a26a24d0544ac88a0cd0 X-Git-Newrev: 01709b16efdbf46496f2110ad2f414fca25813c3 Message-Id: <20230315140453.0CDD23858298@sourceware.org> Date: Wed, 15 Mar 2023 14:04:53 +0000 (GMT) List-Id: https://gcc.gnu.org/g:01709b16efdbf46496f2110ad2f414fca25813c3 commit 01709b16efdbf46496f2110ad2f414fca25813c3 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* } } */