From: Peter Maydell <peter.maydell@linaro.org>
To: Taylor Simpson <tsimpson@quicinc.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
richard.henderson@linaro.org, philmd@linaro.org, ale@rev.ng,
anjo@rev.ng, bcain@quicinc.com, quic_mathbern@quicinc.com
Subject: Re: [PATCH v2] target/hexagon: fix = vs. == mishap
Date: Sat, 29 Apr 2023 10:27:16 +0100 [thread overview]
Message-ID: <CAFEAcA-EG33Ak0S===j8uh0wXEDcNPx7R+GAxF5ad8ptpNZGzQ@mail.gmail.com> (raw)
In-Reply-To: <20230428204411.1400931-1-tsimpson@quicinc.com>
On Fri, 28 Apr 2023 at 21:45, Taylor Simpson <tsimpson@quicinc.com> wrote:
>
> From: Paolo Bonzini <pbonzini@redhat.com>
>
> **** Changes in v2 ****
> Fix yyassert's for sign and zero extends
>
> Coverity reports a parameter that is "set but never used". This is caused
> by an assignment operator being used instead of equality.
The commit message says it's fixing yyasserts, but the
new changed code doesn't seem to be fixing yyasserts?
> Co-authored-by: Taylor Simpson <tsimpson@quicinc.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Taylor Simpson <tsimpson@quicinc.com>
> ---
> target/hexagon/idef-parser/parser-helpers.c | 2 +-
> target/hexagon/idef-parser/idef-parser.y | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/target/hexagon/idef-parser/parser-helpers.c b/target/hexagon/idef-parser/parser-helpers.c
> index 86511efb62..0a01ec39b7 100644
> --- a/target/hexagon/idef-parser/parser-helpers.c
> +++ b/target/hexagon/idef-parser/parser-helpers.c
> @@ -1123,7 +1123,7 @@ HexValue gen_extend_op(Context *c,
> HexValue *value,
> HexSignedness signedness)
> {
> - unsigned bit_width = (dst_width = 64) ? 64 : 32;
> + unsigned bit_width = (dst_width == 64) ? 64 : 32;
> HexValue value_m = *value;
> HexValue src_width_m = *src_width;
>
> diff --git a/target/hexagon/idef-parser/idef-parser.y b/target/hexagon/idef-parser/idef-parser.y
> index 5444fd4749..2561f0ebb0 100644
> --- a/target/hexagon/idef-parser/idef-parser.y
> +++ b/target/hexagon/idef-parser/idef-parser.y
> @@ -685,7 +685,7 @@ rvalue : FAIL
> yyassert(c, &@1, $5.type == IMMEDIATE &&
> $5.imm.type == VALUE,
> "SXT expects immediate values\n");
> - $$ = gen_extend_op(c, &@1, &$3, $5.imm.value, &$7, SIGNED);
> + $$ = gen_extend_op(c, &@1, &$3, 64, &$7, SIGNED);
> }
> | ZXT '(' rvalue ',' IMM ',' rvalue ')'
> {
> @@ -693,7 +693,7 @@ rvalue : FAIL
> yyassert(c, &@1, $5.type == IMMEDIATE &&
> $5.imm.type == VALUE,
> "ZXT expects immediate values\n");
> - $$ = gen_extend_op(c, &@1, &$3, $5.imm.value, &$7, UNSIGNED);
> + $$ = gen_extend_op(c, &@1, &$3, 64, &$7, UNSIGNED);
> }
> | '(' rvalue ')'
> {
> --
> 2.25.1
thanks
-- PMM
next prev parent reply other threads:[~2023-04-29 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 20:44 [PATCH v2] target/hexagon: fix = vs. == mishap Taylor Simpson
2023-04-29 9:27 ` Peter Maydell [this message]
2023-04-29 19:47 ` Taylor Simpson
2023-04-29 12:23 ` Paolo Bonzini
2023-04-29 19:27 ` Taylor Simpson
2023-05-04 14:55 ` Anton Johansson via
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='CAFEAcA-EG33Ak0S===j8uh0wXEDcNPx7R+GAxF5ad8ptpNZGzQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=richard.henderson@linaro.org \
--cc=tsimpson@quicinc.com \
/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).