From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] [libstdc++] [testsuite] xfail double-prec from_chars for float128_t
Date: Thu, 18 Apr 2024 08:10:57 -0300 [thread overview]
Message-ID: <orle5b9b9a.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <or8r1ef10j.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Tue, 16 Apr 2024 00:18:52 -0300")
On Apr 16, 2024, Alexandre Oliva <oliva@adacore.com> wrote:
> * testsuite/20_util/to_chars/float128-c++23.cc: Xfail run on
> aarch64-vxworks.
FTR, here's the fixed ChangeLog entry I'm putting in: (s/-/_/)
* testsuite/20_util/to_chars/float128_c++23.cc: Xfail run on
aarch64-vxworks.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
prev parent reply other threads:[~2024-04-18 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 3:18 Alexandre Oliva
2024-04-16 6:38 ` Jonathan Wakely
2024-04-18 11:10 ` Alexandre Oliva [this message]
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=orle5b9b9a.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).