From: Joseph Myers <joseph@codesourcery.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: <gcc-patches@gcc.gnu.org>, David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: xfail fetestexcept test - ppc always uses fcmpu
Date: Wed, 10 Mar 2021 22:33:09 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2103102231310.797684@digraph.polyomino.org.uk> (raw)
In-Reply-To: <orim5zcrex.fsf@lxoliva.fsfla.org>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-03-10 22:33 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 [this message]
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
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=alpine.DEB.2.22.394.2103102231310.797684@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@adacore.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).