From: Richard Henderson <rth@twiddle.net>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/7] target-tricore: Add FPU infrastructure
Date: Sat, 12 Mar 2016 14:03:37 -0800 [thread overview]
Message-ID: <56E49239.30909@twiddle.net> (raw)
In-Reply-To: <1457708597-3025-2-git-send-email-kbastian@mail.uni-paderborn.de>
On 03/11/2016 07:03 AM, Bastian Koppelmann wrote:
> This patch adds a file for all the FPU related helpers with all the includes,
> useful defines, and a function to update the status bits. Additionally it adds
> a mask for the rounding mode bits of PSW as well as all the opcodes for the
> FPU instructions.
>
> Signed-off-by: Bastian Koppelmann<kbastian@mail.uni-paderborn.de>
> ---
> v3 -> v4:
> - re-introduce f_get_excp_flags which explicitly states which flags to use
> - actually remove double check on float_flag_invalid in f_update_psw_flags()
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
next prev parent reply other threads:[~2016-03-12 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 15:03 [Qemu-devel] [PATCH v4 0/7] TriCore FPU patches Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 1/7] target-tricore: Add FPU infrastructure Bastian Koppelmann
2016-03-12 22:03 ` Richard Henderson [this message]
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 2/7] target-tricore: Move general CHECK_REG_PAIR of decode_rrr_divide Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 3/7] target-tricore: add add.f/sub.f instructions Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 4/7] target-tricore: Add mul.f instruction Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 5/7] target-tricore: Add div.f instruction Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 6/7] target-tricore: Add cmp.f instruction Bastian Koppelmann
2016-03-11 15:03 ` [Qemu-devel] [PATCH v4 7/7] target-tricore: Add ftoi and itof instructions Bastian Koppelmann
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=56E49239.30909@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).