All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rashmica Gupta <rashmica.g@gmail.com>
To: "Víctor Colombo" <victor.colombo@eldorado.org.br>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: clg@kaod.org, danielhb413@gmail.com, david@gibson.dropbear.id.au,
	 groug@kaod.org, richard.henderson@linaro.org
Subject: Re: [PATCH v2 2/3] target/ppc: Fix FPSCR.FI changing in float_overflow_excp()
Date: Wed, 11 May 2022 20:12:14 +1000	[thread overview]
Message-ID: <457382f10aac806ede80ffa013f9fbf3e263c075.camel@gmail.com> (raw)
In-Reply-To: <20220510204610.100867-3-victor.colombo@eldorado.org.br>

[-- Attachment #1: Type: text/plain, Size: 3858 bytes --]

On Tue, 2022-05-10 at 17:46 -0300, Víctor Colombo wrote:
> This patch fixes another not-so-clear situation in Power ISA
> regarding the inexact bits in FPSCR. The ISA states that:
> 
> """
> When Overflow Exception is disabled (OE=0) and an
> Overflow Exception occurs, the following actions are
> taken:
> ...
> 2. Inexact Exception is set
> XX <- 1
> ...
> FI is set to 1
> ...
> """
> 
> However, when tested on a Power 9 hardware, some instructions that
> trigger an OX don't set the FI bit:
> 
> xvcvdpsp(0x4050533fcdb7b95ff8d561c40bf90996) = FI: CLEARED -> CLEARED
> xvnmsubmsp(0xf3c0c1fc8f3230, 0xbeaab9c5) = FI: CLEARED -> CLEARED
> (just a few examples. Other instructions are also affected)

I agree that the ISA could be clearer. These instructions are actually
listed in '7.4.3 Floating-Point Overflow Exception' as instructions
that don't modify FR, FI and FPRF. It would be ideal if the ISA
mentioned that there were exceptions in the part that you quoted!

This patch makes sense to me.

Reviewed-by: Rashmica Gupta <rashmica.g@gmail.com>

> 
> The root cause for this seems to be that only instructions that list
> the bit FI in the "Special Registers Altered" should modify it.
> 
> QEMU is, today, not working like the hardware:
> 
> xvcvdpsp(0x4050533fcdb7b95ff8d561c40bf90996) = FI: CLEARED -> SET
> xvnmsubmsp(0xf3c0c1fc8f3230, 0xbeaab9c5) = FI: CLEARED -> SET
> 
> (all tests assume FI is cleared beforehand)
> 
> Fix this by making float_overflow_excp() return float_flag_inexact
> if it should update the inexact flags.
> 
> Signed-off-by: Víctor Colombo <victor.colombo@eldorado.org.br>
> 
> ---
> 
> v2:
> - remove the setting of FI from float_overflow_excp, making
>   do_float_check_status() the only responsible for it.
> - make float_overflow_excp() return float_flag_inexact if it should
>   update the inexact flags.
> ---
>  target/ppc/fpu_helper.c | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/target/ppc/fpu_helper.c b/target/ppc/fpu_helper.c
> index f1ea4aa10e..88f9e756a5 100644
> --- a/target/ppc/fpu_helper.c
> +++ b/target/ppc/fpu_helper.c
> @@ -329,24 +329,25 @@ static inline void
> float_zero_divide_excp(CPUPPCState *env, uintptr_t raddr)
>      }
>  }
>  
> -static inline void float_overflow_excp(CPUPPCState *env)
> +static inline int float_overflow_excp(CPUPPCState *env)
>  {
>      CPUState *cs = env_cpu(env);
>  
>      env->fpscr |= FP_OX;
>      /* Update the floating-point exception summary */
>      env->fpscr |= FP_FX;
> -    if (env->fpscr & FP_OE) {
> +
> +    bool overflow_enabled = !!(env->fpscr & FP_OE);
> +    if (overflow_enabled) {
>          /* XXX: should adjust the result */
>          /* Update the floating-point enabled exception summary */
>          env->fpscr |= FP_FEX;
>          /* We must update the target FPR before raising the
> exception */
>          cs->exception_index = POWERPC_EXCP_PROGRAM;
>          env->error_code = POWERPC_EXCP_FP | POWERPC_EXCP_FP_OX;
> -    } else {
> -        env->fpscr |= FP_XX;
> -        env->fpscr |= FP_FI;
>      }
> +
> +    return overflow_enabled ? 0 : float_flag_inexact;
>  }
>  
>  static inline void float_underflow_excp(CPUPPCState *env)
> @@ -468,7 +469,7 @@ static void do_float_check_status(CPUPPCState
> *env, bool change_fi,
>      int status = get_float_exception_flags(&env->fp_status);
>  
>      if (status & float_flag_overflow) {
> -        float_overflow_excp(env);
> +        status |= float_overflow_excp(env);
>      } else if (status & float_flag_underflow) {
>          float_underflow_excp(env);
>      }


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-05-11 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 20:46 [PATCH v2 0/3] target/ppc: Fix FPSCR.FI bit Víctor Colombo
2022-05-10 20:46 ` [PATCH v2 1/3] target/ppc: Fix FPSCR.FI bit being cleared when it shouldn't Víctor Colombo
2022-05-10 23:56   ` Richard Henderson
2022-05-11 10:12   ` Rashmica Gupta
2022-05-11 18:29     ` Víctor Colombo
2022-05-10 20:46 ` [PATCH v2 2/3] target/ppc: Fix FPSCR.FI changing in float_overflow_excp() Víctor Colombo
2022-05-10 23:58   ` Richard Henderson
2022-05-11 10:12   ` Rashmica Gupta [this message]
2022-05-10 20:46 ` [PATCH v2 3/3] target/ppc: Rename sfprf to sfifprf where it's also used as set fi flag Víctor Colombo
2022-05-10 23:58   ` Richard Henderson
2022-05-11 10:12   ` Rashmica Gupta

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=457382f10aac806ede80ffa013f9fbf3e263c075.camel@gmail.com \
    --to=rashmica.g@gmail.com \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=victor.colombo@eldorado.org.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.