From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Artyom Tarasenko <atar4qemu@gmail.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <richard.henderson@linaro.org>,
Laurent Vivier <laurent@vivier.eu>
Subject: target/sparc: What is CPU_FEATURE_FLOAT128 for?
Date: Mon, 18 Sep 2023 14:31:57 +0200 [thread overview]
Message-ID: <59e5fc47-cd15-f7b5-a0f7-c0620de33576@linaro.org> (raw)
Hi Mark, Artyom,
I'm looking at the CPU_FEATURE_FLOAT128 definition introduced
in commit 64a88d5d3a ("CPU feature selection support"). Any
clue how it was supposed to be used?
Thanks,
Phil.
next reply other threads:[~2023-09-18 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:31 Philippe Mathieu-Daudé [this message]
2023-09-19 9:32 ` target/sparc: What is CPU_FEATURE_FLOAT128 for? Richard Henderson
2023-09-21 10:23 ` Philippe Mathieu-Daudé
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=59e5fc47-cd15-f7b5-a0f7-c0620de33576@linaro.org \
--to=philmd@linaro.org \
--cc=atar4qemu@gmail.com \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 NNTP newsgroup(s).