From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
michael@amarulasolutions.com, linux-amarula@amarulasolutions.com
Subject: Re: [PATCH 1/1] tests/fp/meson: don't build fp-bench test if fenv.h is missing
Date: Tue, 30 Apr 2024 18:02:20 +0100 [thread overview]
Message-ID: <8734r24wdf.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240430164752.645521-1-dario.binacchi@amarulasolutions.com> (Dario Binacchi's message of "Tue, 30 Apr 2024 18:47:52 +0200")
Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:
> The fp-bench test (i. e. tests/fp/fp-bench.c) use fenv.h that is not
> always provided by the libc (uClibc). The patch disables its compilation
> in case the header is not available.
>
> The patch is based on a suggestion from Paolo Bonzini, which you can
> find at the following link.
>
> Link: https://lists.nongnu.org/archive/html/qemu-devel/2021-03/msg00492.html
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Acked-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-04-30 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 16:47 [PATCH 1/1] tests/fp/meson: don't build fp-bench test if fenv.h is missing Dario Binacchi
2024-04-30 17:02 ` Alex Bennée [this message]
2024-04-30 18:15 ` Richard Henderson
2024-05-01 12:18 ` Dario Binacchi
2024-05-01 13:31 ` Richard Henderson
2024-05-01 14:17 ` Dario Binacchi
2024-05-11 10:11 ` Dario Binacchi
2024-05-11 10:25 ` Richard Henderson
2024-05-11 11:09 ` Dario Binacchi
2024-05-13 10:10 ` Thomas Huth
2024-05-13 12:21 ` Alex Bennée
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=8734r24wdf.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 NNTP newsgroup(s).