From: Richard Henderson <richard.henderson@linaro.org>
To: Feiyang Chen <chris.chenfeiyang@gmail.com>, gaosong@loongson.cn
Cc: c@jia.je, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/loongarch: Remove avail_64 in trans_srai_w()
Date: Mon, 17 Jun 2024 11:09:22 -0700 [thread overview]
Message-ID: <3afda005-7184-4378-be7d-5ffa0e1ca1dd@linaro.org> (raw)
In-Reply-To: <20240617130732.40183-1-chris.chenfeiyang@gmail.com>
On 6/17/24 06:07, Feiyang Chen wrote:
> Since srai.w is a valid instruction on la32, simply remove the avail_64 check.
>
> Fixes: c0c0461e3a06 ("target/loongarch: Add avail_64 to check la64-only instructions")
> Signed-off-by: Feiyang Chen <chris.chenfeiyang@gmail.com>
> ---
> target/loongarch/tcg/insn_trans/trans_shift.c.inc | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/target/loongarch/tcg/insn_trans/trans_shift.c.inc b/target/loongarch/tcg/insn_trans/trans_shift.c.inc
> index 2f4bd6ff28..8bcf341b22 100644
> --- a/target/loongarch/tcg/insn_trans/trans_shift.c.inc
> +++ b/target/loongarch/tcg/insn_trans/trans_shift.c.inc
> @@ -72,10 +72,6 @@ static bool trans_srai_w(DisasContext *ctx, arg_srai_w *a)
> TCGv dest = gpr_dst(ctx, a->rd, EXT_NONE);
> TCGv src1 = gpr_src(ctx, a->rj, EXT_ZERO);
>
> - if (!avail_64(ctx)) {
> - return false;
> - }
> -
> tcg_gen_sextract_tl(dest, src1, a->imm, 32 - a->imm);
> gen_set_gpr(a->rd, dest, EXT_NONE);
>
For the bug fix alone:
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
I'm not sure why this trans function is handled specially.
I think this would be better as
static void gen_sari_w(TCGv dest, TCGv src1, target_long imm)
{
tcg_gen_sextract_tl(dest, src1, imm, 32 - imm);
}
TRANS(sari_w, ALL, gen_rri_c, EXT_NONE, EXT_NONE, gen_sari_w)
r~
prev parent reply other threads:[~2024-06-17 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 13:07 [PATCH] target/loongarch: Remove avail_64 in trans_srai_w() Feiyang Chen
2024-06-17 18:09 ` Richard Henderson [this message]
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=3afda005-7184-4378-be7d-5ffa0e1ca1dd@linaro.org \
--to=richard.henderson@linaro.org \
--cc=c@jia.je \
--cc=chris.chenfeiyang@gmail.com \
--cc=gaosong@loongson.cn \
--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).