From: Richard Henderson <richard.henderson@linaro.org>
To: Ian Jiang <ianjiang.ict@gmail.com>, qemu-devel@nongnu.org
Cc: palmer@dabbelt.com, Alistair.Francis@wdc.com,
sagark@eecs.berkeley.edu, kbastian@mail.uni-paderborn.de
Subject: Re: [PATCH] riscv: Format Rd of FMV.W.X with NoN-boxing
Date: Tue, 21 Jan 2020 22:53:27 -1000 [thread overview]
Message-ID: <b9084f13-0836-7f74-a870-608bf3f8f6a9@linaro.org> (raw)
In-Reply-To: <20200122072448.18510-1-ianjiang.ict@gmail.com>
On 1/21/20 9:24 PM, Ian Jiang wrote:
> For FMV.W.X that moves the lower 32 bits of an integer register to a
> floating-point register, Rd should encoded with NoN-boxing scheme.
> Note: This applies to RV64 only.
>
> Signed-off-by: Ian Jiang <ianjiang.ict@gmail.com>
> ---
> target/riscv/insn_trans/trans_rvf.inc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/target/riscv/insn_trans/trans_rvf.inc.c b/target/riscv/insn_trans/trans_rvf.inc.c
> index 172dbfa919..62b7a36567 100644
> --- a/target/riscv/insn_trans/trans_rvf.inc.c
> +++ b/target/riscv/insn_trans/trans_rvf.inc.c
> @@ -368,6 +368,7 @@ static bool trans_fmv_w_x(DisasContext *ctx, arg_fmv_w_x *a)
>
> #if defined(TARGET_RISCV64)
> tcg_gen_mov_i64(cpu_fpr[a->rd], t0);
> + tcg_gen_ori_i64(cpu_fpr[a->rd], cpu_fpr[a->rd], 0xffffffff00000000ULL);
> #else
> tcg_gen_extu_i32_i64(cpu_fpr[a->rd], t0);
> #endif
>
This doesn't look right. There's nothing in the spec that says the nan-boxing
is restricted to rv64. NaN-boxing is all about FLEN, not XLEN.
r~
next prev parent reply other threads:[~2020-01-22 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 7:24 [PATCH] riscv: Format Rd of FMV.W.X with NoN-boxing Ian Jiang
2020-01-22 8:53 ` Richard Henderson [this message]
2020-01-22 9:53 ` Ian Jiang
2020-01-22 17:10 ` Richard Henderson
2020-01-23 0:48 ` Ian Jiang
2020-01-23 3:07 ` Richard Henderson
2020-01-23 4:05 ` Ian Jiang
2020-01-23 18:52 ` Richard Henderson
2020-01-27 14:17 ` Ian Jiang
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=b9084f13-0836-7f74-a870-608bf3f8f6a9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=ianjiang.ict@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).