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/93355] Analyzer -Wanalysis-too-complex on intl/localealias.c due to poor call summarization
Date: Fri, 12 Mar 2021 20:10:50 +0000 [thread overview]
Message-ID: <bug-93355-4-POZvmffM6a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93355-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93355
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Missing diagnostic for |Analyzer
|missing fclose in |-Wanalysis-too-complex on
|intl/localealias.c |intl/localealias.c due to
| |poor call summarization
Blocks| |99390
--- Comment #12 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #11)
> The only remaining issue is (a) (see comment #9 above).
Updating Summary accordingly, and adding to call summaries tracker
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99390
[Bug 99390] [meta-bug] tracker bug for call summaries in -fanalyzer
prev parent reply other threads:[~2021-03-12 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93355-4@http.gcc.gnu.org/bugzilla/>
2020-09-21 22:49 ` [Bug analyzer/93355] Missing diagnostic for missing fclose in intl/localealias.c cvs-commit at gcc dot gnu.org
2020-09-24 1:26 ` cvs-commit at gcc dot gnu.org
2021-01-26 21:33 ` dmalcolm at gcc dot gnu.org
2021-02-02 2:53 ` cvs-commit at gcc dot gnu.org
2021-02-02 2:55 ` cvs-commit at gcc dot gnu.org
2021-02-02 14:38 ` dmalcolm at gcc dot gnu.org
2021-03-04 0:27 ` dmalcolm at gcc dot gnu.org
2021-03-05 23:54 ` dmalcolm at gcc dot gnu.org
2021-03-11 22:48 ` cvs-commit at gcc dot gnu.org
2021-03-11 23:18 ` dmalcolm at gcc dot gnu.org
2021-03-12 20:10 ` 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-93355-4-POZvmffM6a@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).