* [committed] analyzer: show program point in -Wanalyzer-too-complex
@ 2020-09-16 23:08 David Malcolm
0 siblings, 0 replies; only message in thread
From: David Malcolm @ 2020-09-16 23:08 UTC (permalink / raw)
To: gcc-patches
I found this useful when debugging.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as 6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea.
gcc/analyzer/ChangeLog:
* engine.cc (exploded_graph::get_or_create_node): Show the
program point when issuing -Wanalyzer-too-complex due to hitting
the per-program-point limit.
---
gcc/analyzer/engine.cc | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc
index 49701b74fd4..8f5c5143ca5 100644
--- a/gcc/analyzer/engine.cc
+++ b/gcc/analyzer/engine.cc
@@ -1982,6 +1982,7 @@ exploded_graph::get_or_create_node (const program_point &point,
> param_analyzer_max_enodes_per_program_point)
{
pretty_printer pp;
+ point.print (&pp, format (false));
print_enode_indices (&pp, per_point_data->m_enodes);
if (logger)
logger->log ("not creating enode; too many at program point: %s",
--
2.26.2
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-09-16 23:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-16 23:08 [committed] analyzer: show program point in -Wanalyzer-too-complex David Malcolm
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).