From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [committed 0/8] Use std::unique_ptr in analyzer
Date: Thu, 3 Nov 2022 13:51:27 -0400 [thread overview]
Message-ID: <20221103175135.2269543-1-dmalcolm@redhat.com> (raw)
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-3629-g6341f14e369a5c through
r13-3636-ge177be86c7d327.
David Malcolm (8):
analyzer: use std::unique_ptr for pending_diagnostic/note
analyzer: use std::unique_ptr for saved_diagnostic::m_stmt_finder
analyzer: use std::unique_ptr for custom_edge_info pointers
analyzer: use std::unique_ptr for feasibility_problems and
exploded_path
analyzer: use std::unique_ptr for checker_event
analyzer: use std::unique_ptr during bifurcation
analyzer: use std::unique_ptr for known functions
analyzer: use std::unique_ptr for state machines from plugins
gcc/analyzer/analysis-plan.cc | 1 +
gcc/analyzer/analyzer-pass.cc | 1 +
gcc/analyzer/analyzer-selftests.cc | 1 +
gcc/analyzer/analyzer.cc | 1 +
gcc/analyzer/analyzer.h | 9 +-
gcc/analyzer/call-info.cc | 10 +-
gcc/analyzer/call-string.cc | 1 +
gcc/analyzer/call-summary.cc | 1 +
gcc/analyzer/checker-path.cc | 28 +-
gcc/analyzer/checker-path.h | 4 +-
gcc/analyzer/complexity.cc | 1 +
gcc/analyzer/constraint-manager.cc | 1 +
gcc/analyzer/diagnostic-manager.cc | 257 +++++++++---------
gcc/analyzer/diagnostic-manager.h | 29 +-
gcc/analyzer/engine.cc | 176 ++++++------
gcc/analyzer/exploded-graph.h | 21 +-
gcc/analyzer/feasible-graph.cc | 5 +-
gcc/analyzer/feasible-graph.h | 2 +-
gcc/analyzer/known-function-manager.cc | 6 +-
gcc/analyzer/known-function-manager.h | 2 +-
gcc/analyzer/pending-diagnostic.cc | 14 +-
gcc/analyzer/pending-diagnostic.h | 1 +
gcc/analyzer/program-point.cc | 1 +
gcc/analyzer/program-state.cc | 1 +
gcc/analyzer/region-model-asm.cc | 1 +
gcc/analyzer/region-model-impl-calls.cc | 16 +-
gcc/analyzer/region-model-manager.cc | 1 +
gcc/analyzer/region-model-reachability.cc | 1 +
gcc/analyzer/region-model.cc | 90 +++---
gcc/analyzer/region-model.h | 42 +--
gcc/analyzer/region.cc | 1 +
gcc/analyzer/sm-fd.cc | 58 ++--
gcc/analyzer/sm-file.cc | 10 +-
gcc/analyzer/sm-malloc.cc | 53 ++--
gcc/analyzer/sm-pattern-test.cc | 6 +-
gcc/analyzer/sm-sensitive.cc | 5 +-
gcc/analyzer/sm-signal.cc | 10 +-
gcc/analyzer/sm-taint.cc | 22 +-
gcc/analyzer/sm.cc | 10 +
gcc/analyzer/sm.h | 12 +-
gcc/analyzer/state-purge.cc | 1 +
gcc/analyzer/store.cc | 1 +
gcc/analyzer/supergraph.cc | 1 +
gcc/analyzer/svalue.cc | 1 +
gcc/analyzer/trimmed-graph.cc | 1 +
gcc/analyzer/varargs.cc | 38 +--
.../gcc.dg/plugin/analyzer_gil_plugin.c | 15 +-
.../gcc.dg/plugin/analyzer_kernel_plugin.c | 11 +-
.../gcc.dg/plugin/analyzer_known_fns_plugin.c | 11 +-
49 files changed, 534 insertions(+), 458 deletions(-)
--
2.26.3
next reply other threads:[~2022-11-03 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:51 David Malcolm [this message]
2022-11-03 17:51 ` [committed 1/8] analyzer: use std::unique_ptr for pending_diagnostic/note David Malcolm
2022-11-03 17:51 ` [committed 2/8] analyzer: use std::unique_ptr for saved_diagnostic::m_stmt_finder David Malcolm
2022-11-03 17:51 ` [committed 3/8] analyzer: use std::unique_ptr for custom_edge_info pointers David Malcolm
2022-11-03 17:51 ` [committed 4/8] analyzer: use std::unique_ptr for feasibility_problems and exploded_path David Malcolm
2022-11-03 17:51 ` [committed 5/8] analyzer: use std::unique_ptr for checker_event David Malcolm
2022-11-03 17:51 ` [committed 6/8] analyzer: use std::unique_ptr during bifurcation David Malcolm
2022-11-03 17:51 ` [committed 7/8] analyzer: use std::unique_ptr for known functions David Malcolm
2022-11-03 17:51 ` [committed 8/8] analyzer: use std::unique_ptr for state machines from plugins David Malcolm
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=20221103175135.2269543-1-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@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).