From: Chinmay Rath <rathc@linux.vnet.ibm.com>
To: Richard Henderson <richard.henderson@linaro.org>,
Chinmay Rath <rathc@linux.ibm.com>,
qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, npiggin@gmail.com, danielhb413@gmail.com,
harshpb@linux.ibm.com
Subject: Re: [PATCH 1/8] target/ppc: Move mul{li, lw, lwo, hw, hwu} instructions to decodetree.
Date: Fri, 19 Apr 2024 14:38:16 +0530 [thread overview]
Message-ID: <2203447f-0e3d-4f75-abba-7b8e061783e6@linux.vnet.ibm.com> (raw)
In-Reply-To: <1cb63686-bbb1-4c7a-89ad-51f5da248029@linaro.org>
Hi Richard,
On 4/16/24 23:26, Richard Henderson wrote:
> On 4/15/24 23:39, Chinmay Rath wrote:
>> Moving the following instructions to decodetree specification :
>> mulli : D-form
>> mul{lw, lwo, hw, hwu}[.] : XO-form
>>
>> The changes were verified by validating that the tcg ops generated by
>> those
>> instructions remain the same, which were captured with the '-d
>> in_asm,op' flag.
>>
>> Signed-off-by: Chinmay Rath <rathc@linux.ibm.com>
>> ---
>> target/ppc/insn32.decode | 9 +++
>> target/ppc/translate.c | 89 ----------------------
>> target/ppc/translate/fixedpoint-impl.c.inc | 71 +++++++++++++++++
>> 3 files changed, 80 insertions(+), 89 deletions(-)
>
> This is an accurate reorg of the current code, so
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Thank you.
>
> However, as follow-up, the code generation could be cleaned up:
>
>
>> +static bool trans_MULLW(DisasContext *ctx, arg_MULLW *a)
>> +{
>> +#if defined(TARGET_PPC64)
>> + TCGv_i64 t0, t1;
>> + t0 = tcg_temp_new_i64();
>> + t1 = tcg_temp_new_i64();
>> + tcg_gen_ext32s_tl(t0, cpu_gpr[a->ra]);
>> + tcg_gen_ext32s_tl(t1, cpu_gpr[a->rb]);
>> + tcg_gen_mul_i64(cpu_gpr[a->rt], t0, t1);
>> +#else
>> + tcg_gen_mul_i32(cpu_gpr[a->rt], cpu_gpr[a->ra], cpu_gpr[a->rb]);
>> +#endif
>> + if (unlikely(a->rc)) {
>> + gen_set_Rc0(ctx, cpu_gpr[a->rt]);
>> + }
>> + return true;
>> +}
>
> Without ifdefs:
>
> TCGv t0 = tcg_temp_new();
> TCGv t1 = tcg_temp_new();
>
> tcg_gen_ext32s_tl(t0, ra);
> tcg_gen_ext32s_tl(t1, rb);
> tcg_gen_mul_tl(rt, t0, t1);
>
> For ppc32, ext32s_tl will turn into a mov, which will be optimized
> away. So ideal code generation for both modes.
>
>
>> +static bool trans_MULLWO(DisasContext *ctx, arg_MULLWO *a)
>> +{
>> + TCGv_i32 t0 = tcg_temp_new_i32();
>> + TCGv_i32 t1 = tcg_temp_new_i32();
>> +
>> + tcg_gen_trunc_tl_i32(t0, cpu_gpr[a->ra]);
>> + tcg_gen_trunc_tl_i32(t1, cpu_gpr[a->rb]);
>> + tcg_gen_muls2_i32(t0, t1, t0, t1);
>> +#if defined(TARGET_PPC64)
>> + tcg_gen_concat_i32_i64(cpu_gpr[a->rt], t0, t1);
>> +#else
>> + tcg_gen_mov_i32(cpu_gpr[a->rt], t0);
>> +#endif
>> +
>> + tcg_gen_sari_i32(t0, t0, 31);
>> + tcg_gen_setcond_i32(TCG_COND_NE, t0, t0, t1);
>> + tcg_gen_extu_i32_tl(cpu_ov, t0);
>
> Usually hosts need to create the full 64-bit product and then break it
> apart for tcg_gen_muls2_i32, so split followed immediately by
> concatenate isn't great.
>
>
> TCGv t0 = tcg_temp_new();
> TCGv t1 = tcg_temp_new();
>
> #ifdef TARGET_PPC64
> tcg_gen_ext32s_i64(t0, ra);
> tcg_gen_ext32s_i64(t1, rb);
> tcg_gen_mul_i64(rt, t0, t1);
> tcg_gen_sextract_i64(t0, rt, 31, 1);
> tcg_gen_sari_i64(t1, rt, 32);
> #else
> tcg_gen_muls2_i32(rt, t1, ra, rb);
> tcg_gen_sari_i32(t0, rt, 31);
> #endif
> tcg_gen_setcond_tl(TCG_COND_NE, cpu_ov, t0, t1);
>
Sure, will update in v2.
Thanks,
Chinmay
>
>> + if (is_isa300(ctx)) {
>> + tcg_gen_mov_tl(cpu_ov32, cpu_ov);
>> + }
>> + tcg_gen_or_tl(cpu_so, cpu_so, cpu_ov);
>> +
>> + if (unlikely(a->rc)) {
>> + gen_set_Rc0(ctx, cpu_gpr[a->rt]);
>> + }
>> + return true;
>> +}
>
>
> r~
>
next prev parent reply other threads:[~2024-04-19 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 6:39 [PATCH 0/8] target/ppc: Move fixed-point insns to decodetree Chinmay Rath
2024-04-16 6:39 ` [PATCH 1/8] target/ppc: Move mul{li, lw, lwo, hw, hwu} instructions " Chinmay Rath
2024-04-16 17:56 ` Richard Henderson
2024-04-19 9:08 ` Chinmay Rath [this message]
2024-04-16 6:39 ` [PATCH 2/8] target/ppc: Make divw[u] handler method decodetree compatible Chinmay Rath
2024-04-16 17:57 ` Richard Henderson
2024-04-19 9:17 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 3/8] target/ppc: Move divw[u, e, eu] instructions to decodetree Chinmay Rath
2024-04-16 18:19 ` Richard Henderson
2024-04-19 9:18 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 4/8] target/ppc: Move neg, darn, mod{sw, uw} " Chinmay Rath
2024-04-16 18:25 ` Richard Henderson
2024-04-19 9:18 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 5/8] target/ppc: Move multiply fixed-point insns (64-bit operands) " Chinmay Rath
2024-04-16 18:36 ` Richard Henderson
2024-04-19 9:25 ` Chinmay Rath
2024-04-20 15:51 ` Richard Henderson
2024-04-22 6:32 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 6/8] target/ppc: Move div/mod fixed-point insns (64 bits " Chinmay Rath
2024-04-16 18:38 ` Richard Henderson
2024-04-19 9:26 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 7/8] target/ppc: Move cmp{rb, eqb}, tw[i], td[i], isel instructions " Chinmay Rath
2024-04-16 19:20 ` Richard Henderson
2024-04-19 9:28 ` Chinmay Rath
2024-04-16 6:39 ` [PATCH 8/8] target/ppc: Move logical fixed-point " Chinmay Rath
2024-04-16 19:35 ` Richard Henderson
2024-04-19 9:29 ` Chinmay Rath
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=2203447f-0e3d-4f75-abba-7b8e061783e6@linux.vnet.ibm.com \
--to=rathc@linux.vnet.ibm.com \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.ibm.com \
--cc=richard.henderson@linaro.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).