From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] target/alpha: Do not mix exception flags and FPCR bits
Date: Tue, 11 Feb 2025 08:49:18 -0800 [thread overview]
Message-ID: <52d24c8e-b005-4223-9b26-57885ec3d67d@linaro.org> (raw)
In-Reply-To: <20250211162604.83446-1-philmd@linaro.org>
On 2/11/25 08:26, Philippe Mathieu-Daudé wrote:
> get_float_exception_flags() returns exception flags,
> which are distinct from the FPCR bits used as error code.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> Based-on: <20250211130626.3940412-1-peter.maydell@linaro.org>
> ---
> target/alpha/fpu_helper.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
Yes, this is clearer.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2025-02-11 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 16:26 [PATCH] target/alpha: Do not mix exception flags and FPCR bits Philippe Mathieu-Daudé
2025-02-11 16:49 ` Richard Henderson [this message]
2025-03-06 13:13 ` 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=52d24c8e-b005-4223-9b26-57885ec3d67d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).