From: Richard Henderson <rth@twiddle.net>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/7] target-tricore: add add.f/sub.f instructions
Date: Tue, 8 Mar 2016 13:42:35 -0500 [thread overview]
Message-ID: <56DF1D1B.8000700@twiddle.net> (raw)
In-Reply-To: <1457458958-23933-4-git-send-email-kbastian@mail.uni-paderborn.de>
On 03/08/2016 12:42 PM, Bastian Koppelmann wrote:
> + arg1 = float32_squash_input_denormal(arg1, &env->fp_status); \
> + arg2 = float32_squash_input_denormal(arg2, &env->fp_status); \
> + \
> + f_result = float32_##op(arg2, arg1, &env->fp_status); \
> + flags = f_get_excp_flags(env); \
> + if (flags) { \
float32_squash_input_denormal is the first thing that float32_##op does. No
need to repeat that here.
Otherwise,
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
next prev parent reply other threads:[~2016-03-08 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 17:42 [Qemu-devel] [PATCH v2 0/7] TriCore FPU patches Bastian Koppelmann
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 1/7] target-tricore: Add FPU infrastructure Bastian Koppelmann
2016-03-08 18:26 ` Richard Henderson
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 2/7] target-tricore: Move general CHECK_REG_PAIR of decode_rrr_divide Bastian Koppelmann
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 3/7] target-tricore: add add.f/sub.f instructions Bastian Koppelmann
2016-03-08 18:42 ` Richard Henderson [this message]
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 4/7] target-tricore: Add mul.f instruction Bastian Koppelmann
2016-03-08 18:43 ` Richard Henderson
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 5/7] target-tricore: Add div.f instruction Bastian Koppelmann
2016-03-08 18:43 ` Richard Henderson
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 6/7] target-tricore: Add cmp.f instruction Bastian Koppelmann
2016-03-08 18:44 ` Richard Henderson
2016-03-08 17:42 ` [Qemu-devel] [PATCH v2 7/7] target-tricore: Add ftoi and itof instructions Bastian Koppelmann
2016-03-08 18:44 ` 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=56DF1D1B.8000700@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).