qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Paul Cercueil <paul@crapouillou.net>,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v4 3/4] target/sh4: Rename TCGv variables as manual for ADDV opcode
Date: Wed, 01 May 2024 22:04:25 +0900	[thread overview]
Message-ID: <87r0eladk6.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20240430163125.77430-4-philmd@linaro.org>

On Wed, 01 May 2024 01:31:24 +0900,
Philippe Mathieu-Daudé wrote:
> 
> To easily compare with the SH4 manual, rename:
> 
>   REG(B11_8) -> Rn
>   REG(B7_4) -> Rm
>   t0 -> result
> 
> Mention how overflow is calculated.
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> ---
>  target/sh4/translate.c | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/target/sh4/translate.c b/target/sh4/translate.c
> index 3e013b7c7c..47c0f3404e 100644
> --- a/target/sh4/translate.c
> +++ b/target/sh4/translate.c
> @@ -705,16 +705,20 @@ static void _decode_opc(DisasContext * ctx)
>          return;
>      case 0x300f: /* addv Rm,Rn */
>          {
> -            TCGv t0, t1, t2;
> -            t0 = tcg_temp_new();
> -            tcg_gen_add_i32(t0, REG(B7_4), REG(B11_8));
> +            TCGv Rn = REG(B11_8);
> +            TCGv Rm = REG(B7_4);
> +            TCGv result, t1, t2;
> +
> +            result = tcg_temp_new();
>              t1 = tcg_temp_new();
> -            tcg_gen_xor_i32(t1, t0, REG(B11_8));
>              t2 = tcg_temp_new();
> -            tcg_gen_xor_i32(t2, REG(B7_4), REG(B11_8));
> +            tcg_gen_add_i32(result, Rm, Rn);
> +            /* T = ((Rn ^ Rm) & (Result ^ Rn)) >> 31 */
> +            tcg_gen_xor_i32(t1, result, Rn);
> +            tcg_gen_xor_i32(t2, Rm, Rn);
>              tcg_gen_andc_i32(cpu_sr_t, t1, t2);
>              tcg_gen_shri_i32(cpu_sr_t, cpu_sr_t, 31);
> -            tcg_gen_mov_i32(REG(B11_8), t0);
> +            tcg_gen_mov_i32(Rn, result);
>          }
>          return;
>      case 0x2009: /* and Rm,Rn */
> -- 
> 2.41.0
> 

Reviewed-by: Yoshinori Sato <ysato@users.sourceforge.jp>

-- 
Yosinori Sato


  reply	other threads:[~2024-05-01 13:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 16:31 [PATCH v4 0/4] target/sh4: Fix ADDV/SUBV opcodes Philippe Mathieu-Daudé
2024-04-30 16:31 ` [PATCH v4 1/4] target/sh4: Fix ADDV opcode Philippe Mathieu-Daudé
2024-05-01 12:55   ` Yoshinori Sato
2024-04-30 16:31 ` [PATCH v4 2/4] target/sh4: Fix SUBV opcode Philippe Mathieu-Daudé
2024-05-01 12:56   ` Yoshinori Sato
2024-04-30 16:31 ` [PATCH v4 3/4] target/sh4: Rename TCGv variables as manual for ADDV opcode Philippe Mathieu-Daudé
2024-05-01 13:04   ` Yoshinori Sato [this message]
2024-04-30 16:31 ` [PATCH v4 4/4] target/sh4: Rename TCGv variables as manual for SUBV opcode Philippe Mathieu-Daudé
2024-05-01 13:04   ` Yoshinori Sato
2024-05-03 12:54 ` [PATCH v4 0/4] target/sh4: Fix ADDV/SUBV opcodes Philippe Mathieu-Daudé

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=87r0eladk6.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=paul@crapouillou.net \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --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).