public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: HaoChen Gui <guihaoc@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-133] rs6000: xfail float128 comparison test case that fails on powerpc64.
Date: Fri, 21 Apr 2023 08:44:56 +0000 (GMT)	[thread overview]
Message-ID: <20230421084456.2EE7D3858422@sourceware.org> (raw)

https://gcc.gnu.org/g:6afa7d31a0e8865e17b317ada5cc5014b5d07da3

commit r14-133-g6afa7d31a0e8865e17b317ada5cc5014b5d07da3
Author: Haochen Gui <guihaoc@gcc.gnu.org>
Date:   Fri Apr 21 16:42:31 2023 +0800

    rs6000: xfail float128 comparison test case that fails on powerpc64.
    
    This patch xfails a float128 comparison test case on powerpc64 that
    fails due to a longstanding issue with floating-point compares.
    
    See PR58684 for more information.
    
    When float128 hardware is enabled (-mfloat128-hardware), xscmpuqp is
    generated for comparison which is unexpected.   When float128 software
    emulation is enabled (-mno-float128-hardware), we still have to xfail
    the hardware version (__lekf2_hw) which finally generates xscmpuqp.
    
    gcc/testsuite/
            PR target/108728
            * gcc.dg/torture/float128-cmp-invalid.c: Add xfail.

Diff:
---
 gcc/testsuite/gcc.dg/torture/float128-cmp-invalid.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.dg/torture/float128-cmp-invalid.c b/gcc/testsuite/gcc.dg/torture/float128-cmp-invalid.c
index 1f675efdd61..a86592b3328 100644
--- a/gcc/testsuite/gcc.dg/torture/float128-cmp-invalid.c
+++ b/gcc/testsuite/gcc.dg/torture/float128-cmp-invalid.c
@@ -1,5 +1,6 @@
 /* Test for "invalid" exceptions from __float128 comparisons.  */
 /* { dg-do run } */
+/* { dg-xfail-run-if "xfail for ppc float128_hw" { ppc_float128_hw || { ppc_cpu_supports_hw && p9vector_hw } } } */
 /* { dg-options "" } */
 /* { dg-require-effective-target __float128 } */
 /* { dg-require-effective-target base_quadfloat_support } */

                 reply	other threads:[~2023-04-21  8:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230421084456.2EE7D3858422@sourceware.org \
    --to=guihaoc@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: link
Be 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).