qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>,
	peter.maydell@linaro.org, armbru@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] target-sparc: fix 32-bit truncation in fpackfix, avoid undefined behavior
Date: Fri, 06 Nov 2015 16:28:29 +0000	[thread overview]
Message-ID: <563CD52D.6000607@ilande.co.uk> (raw)
In-Reply-To: <1446825056-7989-1-git-send-email-pbonzini@redhat.com>

On 06/11/15 15:50, Paolo Bonzini wrote:

> This is reported by Coverity.  The algorithm description at
> ftp://ftp.icm.edu.pl/packages/ggi/doc/hw/sparc/Sparc.pdf suggests
> that the 32-bit parts of rs2, after the left shift, is treated
> as a 64-bit integer.  Bits 32 and above are used to do the
> saturating truncation.
> 
> Use a cast to unsigned in order to placate ubsan for negative
> inputs, and do so in the other fpack* instructions too.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  target-sparc/vis_helper.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/target-sparc/vis_helper.c b/target-sparc/vis_helper.c
> index 383cc8b..a1c3343 100644
> --- a/target-sparc/vis_helper.c
> +++ b/target-sparc/vis_helper.c
> @@ -404,7 +404,8 @@ uint32_t helper_fpack16(uint64_t gsr, uint64_t rs2)
>      for (byte = 0; byte < 4; byte++) {
>          uint32_t val;
>          int16_t src = rs2 >> (byte * 16);
> -        int32_t scaled = src << scale;
> +        /* The cast to unsigned avoids undefined behavior for negative src.  */
> +        int32_t scaled = (uint32_t)src << scale;
>          int32_t from_fixed = scaled >> 7;
>  
>          val = (from_fixed < 0 ?  0 :
> @@ -426,7 +427,8 @@ uint64_t helper_fpack32(uint64_t gsr, uint64_t rs1, uint64_t rs2)
>      for (word = 0; word < 2; word++) {
>          uint64_t val;
>          int32_t src = rs2 >> (word * 32);
> -        int64_t scaled = (int64_t)src << scale;
> +        /* The cast to unsigned avoids undefined behavior for negative src.  */
> +        int64_t scaled = (uint64_t)src << scale;
>          int64_t from_fixed = scaled >> 23;
>  
>          val = (from_fixed < 0 ? 0 :
> @@ -447,7 +449,8 @@ uint32_t helper_fpackfix(uint64_t gsr, uint64_t rs2)
>      for (word = 0; word < 2; word++) {
>          uint32_t val;
>          int32_t src = rs2 >> (word * 32);
> -        int64_t scaled = src << scale;
> +        /* The cast to unsigned avoids undefined behavior for negative src.  */
> +        int64_t scaled = (uint64_t)src << scale;
>          int64_t from_fixed = scaled >> 16;
>  
>          val = (from_fixed < -32768 ? -32768 :

Acked-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>


ATB,

Mark.

      parent reply	other threads:[~2015-11-06 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 15:50 [Qemu-devel] [PATCH] target-sparc: fix 32-bit truncation in fpackfix, avoid undefined behavior Paolo Bonzini
2015-11-06 16:10 ` Richard Henderson
2015-11-06 16:28 ` Mark Cave-Ayland [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=563CD52D.6000607@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=armbru@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).