[gcc r11-3243] analyzer: show program point in -Wanalyzer-too-complex
David Malcolm
dmalcolm@gcc.gnu.org
Wed Sep 16 22:59:33 GMT 2020
https://gcc.gnu.org/g:6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea
commit r11-3243-g6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea
Author: David Malcolm <dmalcolm@redhat.com>
Date: Tue Sep 15 09:57:36 2020 -0400
analyzer: show program point in -Wanalyzer-too-complex
I found this useful when debugging.
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.
Diff:
---
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",
More information about the Gcc-cvs
mailing list