From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Mike Stump <mikestump@comcast.net>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Kewen Lin <linkw@gcc.gnu.org>,
gcc-patches@gcc.gnu.org, Joseph Myers <josmyers@redhat.com>
Subject: Re: [PATCH v2] xfail fetestexcept test - ppc always uses fcmpu
Date: Tue, 23 Apr 2024 16:57:52 +0800 [thread overview]
Message-ID: <7df48597-7412-7b97-272a-4d92b6e87ee9@linux.ibm.com> (raw)
In-Reply-To: <orjzkpn2dw.fsf_-_@lxoliva.fsfla.org>
Hi,
on 2024/4/22 18:00, Alexandre Oliva wrote:
> On Mar 10, 2021, Joseph Myers <joseph@codesourcery.com> wrote:
>
>> On Wed, 10 Mar 2021, Alexandre Oliva wrote:
>>> 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.
>
>> In my view, such an XFAIL (for a GCC bug as opposed to an environmental
>> issue) should have a comment pointing to a corresponding open bug in GCC
>> Bugzilla. In this case, that's bug 58684.
>
> Thanks for the suggestion, yeah, that makes sense. Fixed in v2 below.
> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566523.html
> Ping?-ish
>
>
> 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.
>
> Regstrapped on x86_64-linux-gnu and ppc64el-linux-gnu. Also tested with
> gcc-13 on ppc64-vx7r2 and ppc-vx7r2. Ok to install?
>
>
> for gcc/testsuite/ChangeLog
>
> PR target/58684
> * gcc.dg/torture/pr91323.c: Expect execution fail on
> powerpc*-*-*.
> ---
> 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 1411fcaa3966c..f188faa3ccf47 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. */
OK, though the proposed comment is slightly different from what's in
the related commit r8-6445-g86145a19abf39f. :) Thanks!
BR,
Kewen
> /* { dg-add-options ieee } */
> /* { dg-require-effective-target fenv_exceptions } */
> /* { dg-skip-if "fenv" { powerpc-ibm-aix* } } */
>
>
next prev parent reply other threads:[~2024-04-23 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:02 Alexandre Oliva
2021-03-10 22:33 ` Joseph Myers
2021-03-11 15:03 ` Alexandre Oliva
2021-03-11 22:03 ` Joseph Myers
2024-04-22 10:00 ` [PATCH v2] " Alexandre Oliva
2024-04-23 8:57 ` Kewen.Lin [this message]
2024-04-28 7:35 ` 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=7df48597-7412-7b97-272a-4d92b6e87ee9@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=josmyers@redhat.com \
--cc=linkw@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--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).