public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/105285] False positive with -Wanalyzer-null-dereference in git.git's reftable/reader.c Date: Wed, 27 Jul 2022 21:55:24 +0000 [thread overview] Message-ID: <bug-105285-4-jn0fSCqn6n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105285-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105285 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:1321183a13540b5c3503586b94c758198471c7b3 commit r12-8631-g1321183a13540b5c3503586b94c758198471c7b3 Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Jul 27 17:38:53 2022 -0400 analyzer: add .fpath.txt dumps to -fdump-analyzer-feasibility (cherry picked from r13-6-gd8586b00dd00a1783862da5f0c8811a740400074) I found this extension to -fdump-analyzer-feasibility very helpful when debugging PR analyzer/105285. gcc/analyzer/ChangeLog: * diagnostic-manager.cc (epath_finder::process_worklist_item): Call dump_feasible_path when a path that reaches the the target enode is found. (epath_finder::dump_feasible_path): New. * engine.cc (feasibility_state::dump_to_pp): New. * exploded-graph.h (feasibility_state::dump_to_pp): New decl. * feasible-graph.cc (feasible_graph::dump_feasible_path): New. * feasible-graph.h (feasible_graph::dump_feasible_path): New decls. * program-point.cc (function_point::print): Fix missing trailing newlines. * program-point.h (program_point::print_source_line): Remove unimplemented decl. gcc/ChangeLog: * doc/invoke.texi (-fdump-analyzer-feasibility): Mention the fpath.txt output. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-07-27 21:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-15 9:39 [Bug analyzer/105285] New: " avarab at gmail dot com 2022-04-15 9:49 ` [Bug analyzer/105285] " avarab at gmail dot com 2022-04-15 9:54 ` avarab at gmail dot com 2022-04-15 15:11 ` dmalcolm at gcc dot gnu.org 2022-04-27 17:56 ` dmalcolm at gcc dot gnu.org 2022-04-27 18:07 ` dmalcolm at gcc dot gnu.org 2022-04-27 18:08 ` dmalcolm at gcc dot gnu.org 2022-04-27 18:08 ` dmalcolm at gcc dot gnu.org 2022-04-27 19:24 ` dmalcolm at gcc dot gnu.org 2022-04-28 17:48 ` cvs-commit at gcc dot gnu.org 2022-04-28 17:51 ` cvs-commit at gcc dot gnu.org 2022-04-28 17:57 ` dmalcolm at gcc dot gnu.org 2022-07-27 21:55 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-27 21:55 ` cvs-commit at gcc dot gnu.org 2022-07-27 22:09 ` 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-105285-4-jn0fSCqn6n@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: linkBe 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).