public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/105887] New: RFE: clang analyzer warnings that GCC's -fanalyzer could implement
Date: Wed, 08 Jun 2022 14:28:25 +0000	[thread overview]
Message-ID: <bug-105887-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105887

            Bug ID: 105887
           Summary: RFE: clang analyzer warnings that GCC's -fanalyzer
                    could implement
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: meta-bug
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org
  Target Milestone: ---

https://clang.llvm.org/docs/analyzer/checkers.html has a handy list of checkers
that the Clang Static Analyzer implements.

There are various useful tests implemented there that we don't yet implement.

Filing this as a tracker bug for RFEs to track implementing more of them.

             reply	other threads:[~2022-06-08 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 14:28 dmalcolm at gcc dot gnu.org [this message]
2022-06-08 17:30 ` [Bug analyzer/105887] [meta-bug] " egallager at gcc dot gnu.org
2022-07-02 17:11 ` tlange at gcc dot gnu.org
2022-07-28 21:37 ` dmalcolm at gcc dot gnu.org
2022-08-05 23:54 ` dmalcolm at gcc dot gnu.org
2022-10-06 20:01 ` dmalcolm at gcc dot gnu.org
2024-06-07 20:47 ` dmalcolm at gcc dot gnu.org

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=bug-105887-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).