From: HAO CHEN GUI <guihaoc@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
David <dje.gcc@gmail.com>, Peter Bergner <bergner@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, rs6000] xfail float128 comparison test case that fails on powerpc64 [PR108728]
Date: Fri, 14 Apr 2023 09:34:33 +0800 [thread overview]
Message-ID: <84c7ea10-5f15-03b8-3354-487665e7e409@linux.ibm.com> (raw)
In-Reply-To: <ccafe1be-57ed-460b-9a37-c19a5b82f86b@linux.ibm.com>
Hi Kewen,
在 2023/4/13 16:32, Kewen.Lin 写道:
> xfail all powerpc*-*-* can have some XPASSes on those ENVs with
> software emulation. Since the related hw insn xscmpuqp is guarded
> with TARGET_FLOAT128_HW, could we use the effective target
> ppc_float128_hw instead?
Thanks for your review comments. It's tricky. It invokes "__lekf2"
with "-mno-float128_hw". But it doesn't always pass the check.
With math library on P8, it can. With the library on P9, it fails.
So it's totally depended on the version of library which is not
controlled by GCC. What's your opinion?
Test result on P9
make check-gcc-c RUNTESTFLAGS="--target_board=unix'{-mno-float128-hardware}' dg-torture.exp=float128-cmp-invalid.c"
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O0 execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O1 execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O3 -g execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -Os execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
=== gcc Summary ===
# of expected passes 7
# of unexpected failures 7
Gui Haochen
Thanks
next prev parent reply other threads:[~2023-04-14 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 2:27 HAO CHEN GUI
2023-04-13 8:32 ` Kewen.Lin
2023-04-14 1:34 ` HAO CHEN GUI [this message]
2023-04-14 5:11 ` Kewen.Lin
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=84c7ea10-5f15-03b8-3354-487665e7e409@linux.ibm.com \
--to=guihaoc@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.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).