Coverity defects for generated Hexagon code
WARNING: This email originated from outside of Qualcomm. Please be wary of
any links or attachments, and do not enable macros.
On 5/23/23 06:29, Anton Johansson via wrote:
On 5/23/23 12:29, Paolo Bonzini wrote:
On Tue, May 23, 2023 at 11:18 AM Peter Maydell
g
> Subject: Re: Help finding Coverity defects for generated Hexagon code
>
> WARNING: This email originated from outside of Qualcomm. Please be wary of
> any links or attachments, and do not enable macros.
>
> On 5/23/23 06:29, Anton Johansson via wrote:
> >
> > On 5/23
On 5/23/23 06:29, Anton Johansson via wrote:
On 5/23/23 12:29, Paolo Bonzini wrote:
On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote:
On Mon, 22 May 2023 at 21:24, Anton Johansson wrote:
Hi,
coverity recently reported some defects in code generated by idef-parser
(email attached). Thes
On 5/23/23 12:29, Paolo Bonzini wrote:
On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote:
On Mon, 22 May 2023 at 21:24, Anton Johansson wrote:
Hi,
coverity recently reported some defects in code generated by idef-parser
(email attached). These defects are expected and we plan to emit a
On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote:
> On Mon, 22 May 2023 at 21:24, Anton Johansson wrote:
> > Hi,
> >
> > coverity recently reported some defects in code generated by idef-parser
> > (email attached). These defects are expected and we plan to emit a
> > /* coverity[event_tag] *
On Mon, 22 May 2023 at 21:24, Anton Johansson wrote:
>
> Hi,
>
> coverity recently reported some defects in code generated by idef-parser
> (email attached). These defects are expected and we plan to emit a
> /* coverity[event_tag] */ comment to disable the specific event triggered.
We don't mark
Hi,
coverity recently reported some defects in code generated by idef-parser
(email attached). These defects are expected and we plan to emit a
/* coverity[event_tag] */ comment to disable the specific event triggered.
However, I'm not able to find the event_tag as I can't find the defect in
the
