Re: [PATCH v2] target/hexagon: fix = vs. == mishap

2023-05-04 Thread Anton Johansson via
On 4/28/23 22:44, Taylor Simpson wrote: From: Paolo Bonzini 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. Co-authored-by: Taylor Simpson S

RE: [PATCH v2] target/hexagon: fix = vs. == mishap

2023-04-29 Thread Taylor Simpson
o (QUIC) > > Subject: Re: [PATCH v2] target/hexagon: fix = vs. == mishap > > WARNING: This email originated from outside of Qualcomm. Please be wary > of any links or attachments, and do not enable macros. > > On Fri, 28 Apr 2023 at 21:45, Taylor Simpson wrote: > > >

RE: [PATCH v2] target/hexagon: fix = vs. == mishap

2023-04-29 Thread Taylor Simpson
> -Original Message- > From: Paolo Bonzini > Sent: Saturday, April 29, 2023 7:24 AM > To: Taylor Simpson ; qemu-devel@nongnu.org > Cc: richard.hender...@linaro.org; phi...@linaro.org; a...@rev.ng; > a...@rev.ng; Brian Cain ; Matheus Bernardino (QUIC) > > Subjec

Re: [PATCH v2] target/hexagon: fix = vs. == mishap

2023-04-29 Thread Paolo Bonzini
On 4/28/23 22:44, Taylor Simpson wrote: From: Paolo Bonzini 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. Co-authored-by: Taylor Simpson Tha

Re: [PATCH v2] target/hexagon: fix = vs. == mishap

2023-04-29 Thread Peter Maydell
On Fri, 28 Apr 2023 at 21:45, Taylor Simpson wrote: > > From: Paolo Bonzini > > 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