public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/112317] New: Latest set of clang warnings
Date: Tue, 31 Oct 2023 16:33:38 +0000	[thread overview]
Message-ID: <bug-112317-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112317
           Summary: Latest set of clang warnings
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

From a clang build of gcc trunk, I get

$ grep /analyzer/ mk.out
../../trunk.year/gcc/analyzer/access-diagram.cc:976:26: warning: private field
'm_col_widths' is not used [-Wunused-private-field]
../../trunk.year/gcc/analyzer/region-model.cc:1914:20: warning: unused variable
'limited_sval' [-Wunused-variable]
../../trunk.year/gcc/analyzer/region-model.cc:1884:16: warning: unused variable
'strlen_sval' [-Wunused-variable]
../../trunk.year/gcc/analyzer/region-model.h:892:8: warning: 'warn' overrides a
member function but is not marked 'override' [-Winconsistent-missing-override]
$ 

Given that these have been hanging around for weeks, it might be worth fixing
them.

             reply	other threads:[~2023-10-31 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 16:33 dcb314 at hotmail dot com [this message]
2023-11-02 12:43 ` [Bug analyzer/112317] " cvs-commit at gcc dot gnu.org
2023-11-02 12:45 ` 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-112317-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).