diff options
| author | David Malcolm <dmalcolm@redhat.com> | 2020-09-15 09:57:36 -0400 |
|---|---|---|
| committer | David Malcolm <dmalcolm@redhat.com> | 2020-09-16 18:58:51 -0400 |
| commit | 6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea (patch) | |
| tree | d33f6322805f92aa3fab22e14877738fdafd4a40 /gcc/analyzer | |
| parent | e097c9ab83192fc2f738ec6426a275282e9a51ea (diff) | |
| download | gcc-6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea.zip gcc-6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea.tar.gz gcc-6dd96e24ea3cb9919fedd4da35fbfd36ed98b0ea.tar.bz2 | |
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.
Diffstat (limited to 'gcc/analyzer')
| -rw-r--r-- | gcc/analyzer/engine.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc index 49701b7..8f5c514 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", |