From: Richard Henderson <rth@twiddle.net>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/7] target-tricore: Add cmp.f instruction
Date: Tue, 1 Mar 2016 10:21:54 -0800 [thread overview]
Message-ID: <56D5DDC2.4000801@twiddle.net> (raw)
In-Reply-To: <1456849468-30217-7-git-send-email-kbastian@mail.uni-paderborn.de>
On 03/01/2016 08:24 AM, Bastian Koppelmann wrote:
> Signed-off-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
> ---
> target-tricore/fpu_helper.c | 29 +++++++++++++++++++++++++++++
> target-tricore/helper.h | 1 +
> target-tricore/translate.c | 3 +++
> 3 files changed, 33 insertions(+)
>
> diff --git a/target-tricore/fpu_helper.c b/target-tricore/fpu_helper.c
> index ee8b687..ceda415 100644
> --- a/target-tricore/fpu_helper.c
> +++ b/target-tricore/fpu_helper.c
> @@ -171,3 +171,32 @@ uint32_t helper_fdiv(CPUTriCoreState *env, uint32_t r1, uint32_t r2)
> f_update_psw_flags(env, true);
> return (uint32_t)f_result;
> }
> +
> +uint32_t helper_fcmp(CPUTriCoreState *env, uint32_t r1, uint32_t r2)
> +{
> + uint32_t result = 0;
> + uint32_t lt, eq, uo;
> + float32 arg1 = make_float32(r1);
> + float32 arg2 = make_float32(r2);
> +
> + set_flush_inputs_to_zero(0, &env->fp_status);
> +
> + lt = float32_lt_quiet(arg1, arg2, &env->fp_status);
> + eq = float32_eq_quiet(arg1, arg2, &env->fp_status);
> + uo = float32_unordered(arg1, arg2, &env->fp_status);
Do it in one step with float32_compare.
You don't want _quiet; see below re psw_flags.
> + env->FPU_FS = 0;
> + if (float32_is_signaling_nan(arg1) || float32_is_signaling_nan(arg2)) {
> + env->FPU_FI = (1 << 31);
> + env->FPU_FS = 1;
> + }
> +
> + return result;
If you return flush_inputs_to_zero to 1 here, you don't have to zero it on all
other fp operations.
Why aren't you using the same f_update_psw_flags function? The only bit that
compare can set is invalid anyway.
r~
next prev parent reply other threads:[~2016-03-01 18:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 16:24 [Qemu-devel] [PATCH 0/7] TriCore FPU patches Bastian Koppelmann
2016-03-01 16:24 ` [Qemu-devel] [PATCH 1/7] target-tricore: Add FPU infrastructure Bastian Koppelmann
2016-03-01 17:46 ` Richard Henderson
2016-03-01 16:24 ` [Qemu-devel] [PATCH 2/7] target-tricore: Move general CHECK_REG_PAIR of decode_rrr_divide Bastian Koppelmann
2016-03-01 17:46 ` Richard Henderson
2016-03-01 16:24 ` [Qemu-devel] [PATCH 3/7] target-tricore: add add.f/sub.f instructions Bastian Koppelmann
2016-03-01 18:10 ` Richard Henderson
2016-03-01 16:24 ` [Qemu-devel] [PATCH 4/7] target-tricore: Add mul.f instruction Bastian Koppelmann
2016-03-01 16:24 ` [Qemu-devel] [PATCH 5/7] target-tricore: Add div.f instruction Bastian Koppelmann
2016-03-01 16:24 ` [Qemu-devel] [PATCH 6/7] target-tricore: Add cmp.f instruction Bastian Koppelmann
2016-03-01 18:21 ` Richard Henderson [this message]
2016-03-08 10:20 ` Bastian Koppelmann
2016-03-08 14:42 ` Richard Henderson
2016-03-08 15:07 ` Bastian Koppelmann
2016-03-08 15:11 ` Bastian Koppelmann
2016-03-08 15:37 ` Richard Henderson
2016-03-08 15:40 ` Bastian Koppelmann
2016-03-01 16:24 ` [Qemu-devel] [PATCH 7/7] target-tricore: Add ftoi and itof instructions Bastian Koppelmann
2016-03-01 18:26 ` Richard Henderson
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=56D5DDC2.4000801@twiddle.net \
--to=rth@twiddle.net \
--cc=kbastian@mail.uni-paderborn.de \
--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).