From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++-v3: testsuite: complex proj requirements
Date: Mon, 27 Jun 2022 11:12:35 +0100 [thread overview]
Message-ID: <CAH6eHdSp4zSziEiRA=5-XhO1fqPmYLMmS6HNyvzu=sa_2RYG2A@mail.gmail.com> (raw)
In-Reply-To: <orbkuezaep.fsf@lxoliva.fsfla.org>
On Mon, 27 Jun 2022 at 11:09, Alexandre Oliva via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> On Jun 21, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
>
> > * testsuite/26_numerics/complex/proj.cc: Skip test in the
> > circumstances in which the implementation of proj is known to
> > be broken.
>
> Ping?
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596922.html
>
> (I've dropped the '-v3' from the summary line after noticing it)
OK
>
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts. Ask me about <https://stallmansupport.org>
prev parent reply other threads:[~2022-06-27 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 5:39 Alexandre Oliva
2022-06-27 10:08 ` Alexandre Oliva
2022-06-27 10:12 ` Jonathan Wakely [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='CAH6eHdSp4zSziEiRA=5-XhO1fqPmYLMmS6HNyvzu=sa_2RYG2A@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=oliva@adacore.com \
/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).