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] [meta-bug] clang analyzer warnings that GCC's -fanalyzer could implement
Date: Thu, 06 Oct 2022 20:01:43 +0000 [thread overview]
Message-ID: <bug-105887-4-KckpRtdO1K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105887-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105887
Bug 105887 depends on bug 106000, which changed state.
Bug 106000 Summary: RFE: -fanalyzer should complain about memory accesses that are definitely out-of-bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106000
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
prev parent reply other threads:[~2022-10-06 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 14:28 [Bug analyzer/105887] New: RFE: " dmalcolm at gcc dot gnu.org
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 [this message]
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-KckpRtdO1K@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).