qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: anjo@rev.ng
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, pbonzini@redhat.com
Subject: Re: Help finding Coverity defects for generated Hexagon code
Date: Tue, 23 May 2023 10:17:46 +0100	[thread overview]
Message-ID: <CAFEAcA9ZctmXrCAwsAk6eBeF4ojB4QBwq16TsdcGZPHTin6LEg@mail.gmail.com> (raw)
In-Reply-To: <4ffdd486-ec7d-49c7-1330-0d0b090735b9@rev.ng>

On Mon, 22 May 2023 at 21:24, Anton Johansson <anjo@rev.ng> 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 coverity false positives with comments in the
source. For the free online scanner, we just mark them as
false positives in the GUI (with an explanation of why they're
false positives).

It's weird that the ones listed in the email don't show up
in the GUI, but if they're not in the GUI as unresolved issues
then they're not a problem :-)

thanks
-- PMM


  reply	other threads:[~2023-05-23  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6467d9133bd9f_57b172b16e2c9d98835043@prd-scan-dashboard-0.mail>
2023-05-22 20:24 ` Help finding Coverity defects for generated Hexagon code Anton Johansson via
2023-05-23  9:17   ` Peter Maydell [this message]
2023-05-23 10:29     ` Paolo Bonzini
2023-05-23 13:29       ` Anton Johansson via
2023-05-23 15:31         ` Richard Henderson
2023-05-23 17:56           ` Brian Cain
2023-06-02 13:18             ` 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=CAFEAcA9ZctmXrCAwsAk6eBeF4ojB4QBwq16TsdcGZPHTin6LEg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=anjo@rev.ng \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).