From: Jonathan Wakely <jwakely@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: require cmath for exp simd
Date: Mon, 27 Jun 2022 12:02:12 +0100 [thread overview]
Message-ID: <CACb0b4nw4A6sRr8WiT6z0Rebkpb9OTv99B4dozbBnAJTncj58w@mail.gmail.com> (raw)
In-Reply-To: <orr13iefxh.fsf@lxoliva.fsfla.org>
On Tue, 21 Jun 2022 at 06:38, Alexandre Oliva via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
>
> simd_math.h assumes declarations for many C99 functions to be present,
> that libstdc++ doesn't add to target systems that don't have them in
> the C library.
>
> Add the C99 math requirement to tests for simd features, so that they
> don't fail because of limitations of the target C library.
>
> Regstrapped on x86_64-linux-gnu, also tested with a cross to
> aarch64-rtems6. Ok to install?
OK
prev parent reply other threads:[~2022-06-27 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 5:36 Alexandre Oliva
2022-06-27 10:20 ` Alexandre Oliva
2022-06-27 11:02 ` 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=CACb0b4nw4A6sRr8WiT6z0Rebkpb9OTv99B4dozbBnAJTncj58w@mail.gmail.com \
--to=jwakely@redhat.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).