From: Joseph Myers <joseph@codesourcery.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: xfail fetestexcept test - ppc always uses fcmpu
Date: Thu, 11 Mar 2021 22:03:58 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2103112203190.879960@digraph.polyomino.org.uk> (raw)
In-Reply-To: <ory2et91gl.fsf@lxoliva.fsfla.org>
On Thu, 11 Mar 2021, Alexandre Oliva wrote:
> I kind of like the notion of adding a comment to the test itself, but I
> wasn't sure that's what you meant.
Yes, adding a comment to the test itself is what I meant.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-03-11 22:04 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 [this message]
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.2103112203190.879960@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).