public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] xfail fetestexcept test - ppc always uses fcmpu Date: Tue, 23 Apr 2024 02:38:51 +0000 (GMT) [thread overview] Message-ID: <20240423023851.B53DD3858289@sourceware.org> (raw) https://gcc.gnu.org/g:2062c8d2122c4b7dc82af9a7114136ca371da5ff commit 2062c8d2122c4b7dc82af9a7114136ca371da5ff Author: Alexandre Oliva <oliva@adacore.com> 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* } } */
next reply other threads:[~2024-04-23 2:38 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 2:38 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-28 5:22 Alexandre Oliva 2024-04-22 6:57 Alexandre Oliva 2024-04-22 5:13 Alexandre Oliva 2024-04-21 20:27 Alexandre Oliva 2023-04-06 6:33 Alexandre Oliva 2023-03-30 14:06 Alexandre Oliva 2023-03-24 6:24 Alexandre Oliva 2023-03-23 3:46 Alexandre Oliva 2023-03-16 14:21 Alexandre Oliva 2023-03-15 14:04 Alexandre Oliva 2021-03-11 10:21 Alexandre Oliva 2021-03-09 21:47 Alexandre Oliva 2021-03-09 21:25 Alexandre Oliva 2021-03-09 2:26 Alexandre Oliva
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240423023851.B53DD3858289@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).