From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2140) id 622A0385841E; Mon, 22 Apr 2024 06:57:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 622A0385841E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1713769042; bh=H8NvJczNkEZMzePm2iST/k+NcY1PXS49b151ny5/7BA=; h=From:To:Subject:Date:From; b=D8cfkgfHmRcHEoou6bZC9fuHsGbQ7myos86/jbWKeON5LKweIAmIMWzEZGx85vHlh uP8qid8bkLtc3oPYlvhLtdmciHs+Es55aZj9HQDVjMxfNIy3lu7T0KfDPtCXOsPIH4 AUHCKpRL8CeOsu0/W5yklQZh2UERMYC18Q/gpzxE= 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: cef88428efe311383bc65c47e4f6c96a8b16452a X-Git-Newrev: 1dd110cf0d45a2716102a53cc42f809e29d909ae Message-Id: <20240422065722.622A0385841E@sourceware.org> Date: Mon, 22 Apr 2024 06:57:22 +0000 (GMT) List-Id: https://gcc.gnu.org/g:1dd110cf0d45a2716102a53cc42f809e29d909ae commit 1dd110cf0d45a2716102a53cc42f809e29d909ae 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..f188faa3ccf 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*-*-* } } */ +/* The ppc xfail is because of PR target/58684. */ /* { dg-add-options ieee } */ /* { dg-require-effective-target fenv_exceptions } */ /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */