From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org,
Lucas Mateus Castro <lucas.araujo@eldorado.org.br>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] target/ppc: fix unreachable code in fpu_helper.c
Date: Mon, 6 Jun 2022 14:50:59 -0300 [thread overview]
Message-ID: <add7db64-071d-ad4a-cd4a-1924a8e7cfdf@gmail.com> (raw)
In-Reply-To: <20220602191048.137511-1-danielhb413@gmail.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 6/2/22 16:10, Daniel Henrique Barboza wrote:
> Commit c29018cc7395 added an env->fpscr OR operation using a ternary
> that checks if 'error' is not zero:
>
> env->fpscr |= error ? FP_FEX : 0;
>
> However, in the current body of do_fpscr_check_status(), 'error' is
> granted to be always non-zero at that point. The result is that Coverity
> is less than pleased:
>
> Control flow issues (DEADCODE)
> Execution cannot reach the expression "0ULL" inside this statement:
> "env->fpscr |= (error ? 1073...".
>
> Remove the ternary and always make env->fpscr |= FP_FEX.
>
> Cc: Lucas Mateus Castro (alqotel) <lucas.araujo@eldorado.org.br>
> Cc: Richard Henderson <richard.henderson@linaro.org>
> Fixes: Coverity CID 1489442
> Fixes: c29018cc7395 ("target/ppc: Implemented xvf*ger*")
> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
> ---
> target/ppc/fpu_helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/ppc/fpu_helper.c b/target/ppc/fpu_helper.c
> index fed0ce420a..7ab6beadad 100644
> --- a/target/ppc/fpu_helper.c
> +++ b/target/ppc/fpu_helper.c
> @@ -464,7 +464,7 @@ static void do_fpscr_check_status(CPUPPCState *env, uintptr_t raddr)
> }
> cs->exception_index = POWERPC_EXCP_PROGRAM;
> env->error_code = error | POWERPC_EXCP_FP;
> - env->fpscr |= error ? FP_FEX : 0;
> + env->fpscr |= FP_FEX;
> /* Deferred floating-point exception after target FPSCR update */
> if (fp_exceptions_enabled(env)) {
> raise_exception_err_ra(env, cs->exception_index,
prev parent reply other threads:[~2022-06-06 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 19:10 [PATCH] target/ppc: fix unreachable code in fpu_helper.c Daniel Henrique Barboza
2022-06-02 20:00 ` Lucas Mateus Martins Araujo e Castro
2022-06-06 17:50 ` Daniel Henrique Barboza [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=add7db64-071d-ad4a-cd4a-1924a8e7cfdf@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=lucas.araujo@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).