qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Frank Chang <0xc0de0125@gmail.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	Frank Chang <frank.chang@sifive.com>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH] target/riscv: fix vssub.vv saturation bug
Date: Mon, 19 Apr 2021 18:49:56 +1000	[thread overview]
Message-ID: <CAKmqyKMJW63O1P0wwKpWXM5QWgy8NCrrMiZzBXw37-JC7Ft_QQ@mail.gmail.com> (raw)
In-Reply-To: <CANzO1D2sRnzezeae89J4P+dBw_h0NSTX2SQUEStNo1K8dyquTQ@mail.gmail.com>

On Mon, Apr 19, 2021 at 4:31 PM Frank Chang <0xc0de0125@gmail.com> wrote:
>
> Alistair Francis <alistair23@gmail.com> 於 2021年4月19日 週一 下午2:28寫道:
>>
>> On Mon, Apr 19, 2021 at 4:02 PM <frank.chang@sifive.com> wrote:
>> >
>> > From: Frank Chang <frank.chang@sifive.com>
>> >
>> > Doing a negate (0x0 – 0x80000000) using vssub.vv produces
>> > an incorrect result of 0x80000000 (should saturate to 0x7fffffff)
>> >
>> > Fix this bug by treating zero as a positive number.
>> >
>> > Signed-off-by: Frank Chang <frank.chang@sifive.com>
>>
>> Thanks for the patch!
>>
>> A similar fix is already in the riscv-to-apply.next queue
>>
>>    target/riscv: Fixup saturate subtract function
>>
>>    The overflow predication ((a - b) ^ a) & (a ^ b) & INT64_MIN is right.
>>    However, when the predication is ture and a is 0, it should return maximum.
>>
>>    Signed-off-by: LIU Zhiwei <zhiwei_liu@c-sky.com>
>>    Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>>    Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
>>    Message-id: 20210212150256.885-4-zhiwei_liu@c-sky.com
>>    Message-Id: <20210212150256.885-4-zhiwei_liu@c-sky.com>
>>
>>
>> Alistair
>
>
> Thanks, I might missed that patch.

No worries. Thanks anyway for the fix.

Alistair

> Frank Chang
>
>>
>>
>> > ---
>> >  target/riscv/vector_helper.c | 8 ++++----
>> >  1 file changed, 4 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/target/riscv/vector_helper.c b/target/riscv/vector_helper.c
>> > index a156573d281..356cef8a090 100644
>> > --- a/target/riscv/vector_helper.c
>> > +++ b/target/riscv/vector_helper.c
>> > @@ -2451,7 +2451,7 @@ static inline int8_t ssub8(CPURISCVState *env, int vxrm, int8_t a, int8_t b)
>> >  {
>> >      int8_t res = a - b;
>> >      if ((res ^ a) & (a ^ b) & INT8_MIN) {
>> > -        res = a > 0 ? INT8_MAX : INT8_MIN;
>> > +        res = a >= 0 ? INT8_MAX : INT8_MIN;
>> >          env->vxsat = 0x1;
>> >      }
>> >      return res;
>> > @@ -2461,7 +2461,7 @@ static inline int16_t ssub16(CPURISCVState *env, int vxrm, int16_t a, int16_t b)
>> >  {
>> >      int16_t res = a - b;
>> >      if ((res ^ a) & (a ^ b) & INT16_MIN) {
>> > -        res = a > 0 ? INT16_MAX : INT16_MIN;
>> > +        res = a >= 0 ? INT16_MAX : INT16_MIN;
>> >          env->vxsat = 0x1;
>> >      }
>> >      return res;
>> > @@ -2471,7 +2471,7 @@ static inline int32_t ssub32(CPURISCVState *env, int vxrm, int32_t a, int32_t b)
>> >  {
>> >      int32_t res = a - b;
>> >      if ((res ^ a) & (a ^ b) & INT32_MIN) {
>> > -        res = a > 0 ? INT32_MAX : INT32_MIN;
>> > +        res = a >= 0 ? INT32_MAX : INT32_MIN;
>> >          env->vxsat = 0x1;
>> >      }
>> >      return res;
>> > @@ -2481,7 +2481,7 @@ static inline int64_t ssub64(CPURISCVState *env, int vxrm, int64_t a, int64_t b)
>> >  {
>> >      int64_t res = a - b;
>> >      if ((res ^ a) & (a ^ b) & INT64_MIN) {
>> > -        res = a > 0 ? INT64_MAX : INT64_MIN;
>> > +        res = a >= 0 ? INT64_MAX : INT64_MIN;
>> >          env->vxsat = 0x1;
>> >      }
>> >      return res;
>> > --
>> > 2.17.1
>> >
>> >


      reply	other threads:[~2021-04-19  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  6:01 [PATCH] target/riscv: fix vssub.vv saturation bug frank.chang
2021-04-19  6:25 ` Alistair Francis
2021-04-19  6:31   ` Frank Chang
2021-04-19  8:49     ` Alistair Francis [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=CAKmqyKMJW63O1P0wwKpWXM5QWgy8NCrrMiZzBXw37-JC7Ft_QQ@mail.gmail.com \
    --to=alistair23@gmail.com \
    --cc=0xc0de0125@gmail.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=frank.chang@sifive.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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).