qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] target/sh4: Avoid shift into sign bit in update_itlb_use()
Date: Wed, 24 Jul 2024 12:00:04 +0900	[thread overview]
Message-ID: <871q3jebpn.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20240723172431.1757296-1-peter.maydell@linaro.org>

On Wed, 24 Jul 2024 02:24:31 +0900,
Peter Maydell wrote:
> 
> In update_itlb_use() the variables or_mask and and_mask are uint8_t,
> which means that in expressions like "and_mask << 24" the usual C
> arithmetic conversions will result in the shift being done as a
> signed int type, and so we will shift into the sign bit. For QEMU
> this isn't undefined behaviour because we use -fwrapv; but we can
> avoid it anyway by using uint32_t types for or_mask and and_mask.
> 
> Resolves: Coverity CID 1547628
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>  target/sh4/helper.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/target/sh4/helper.c b/target/sh4/helper.c
> index 67029106277..9659c695504 100644
> --- a/target/sh4/helper.c
> +++ b/target/sh4/helper.c
> @@ -187,7 +187,7 @@ void superh_cpu_do_interrupt(CPUState *cs)
>  
>  static void update_itlb_use(CPUSH4State * env, int itlbnb)
>  {
> -    uint8_t or_mask = 0, and_mask = (uint8_t) - 1;
> +    uint32_t or_mask = 0, and_mask = 0xff;
>  
>      switch (itlbnb) {
>      case 0:
> -- 
> 2.34.1
> 

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

-- 
Yosinori Sato


  parent reply	other threads:[~2024-07-24  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 17:24 [PATCH] target/sh4: Avoid shift into sign bit in update_itlb_use() Peter Maydell
2024-07-23 20:57 ` Philippe Mathieu-Daudé
2024-07-24  0:23 ` Richard Henderson
2024-07-24  3:00 ` Yoshinori Sato [this message]
2024-07-29 16:00 ` Peter Maydell

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=871q3jebpn.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=peter.maydell@linaro.org \
    --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).