aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorDavid Malcolm <dmalcolm@redhat.com>2022-07-19 09:53:39 -0400
committerDavid Malcolm <dmalcolm@redhat.com>2022-07-19 09:53:39 -0400
commit434d521d118fc7e7759b2b42bdddfa70caec637b (patch)
tree6951b8625a182e89993223f39064666f6f2e2a82 /gcc
parentedf0c132b19f73e5739715c2ac90c4ae1e96dc31 (diff)
downloadgcc-434d521d118fc7e7759b2b42bdddfa70caec637b.zip
gcc-434d521d118fc7e7759b2b42bdddfa70caec637b.tar.gz
gcc-434d521d118fc7e7759b2b42bdddfa70caec637b.tar.bz2
analyzer: log out-edge description in exploded_graph::process_node
I found this logging tweak very helpful when working on PR analyzer/106284. gcc/analyzer/ChangeLog: * engine.cc (exploded_graph::process_node): Show any description of the out-edge when logging it for consideration. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
Diffstat (limited to 'gcc')
-rw-r--r--gcc/analyzer/engine.cc8
1 files changed, 6 insertions, 2 deletions
diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc
index 9ffcc41..4f7f9d0 100644
--- a/gcc/analyzer/engine.cc
+++ b/gcc/analyzer/engine.cc
@@ -3974,8 +3974,12 @@ exploded_graph::process_node (exploded_node *node)
{
found_a_superedge = true;
if (logger)
- logger->log ("considering SN: %i -> SN: %i",
- succ->m_src->m_index, succ->m_dest->m_index);
+ {
+ label_text succ_desc (succ->get_description (false));
+ logger->log ("considering SN: %i -> SN: %i (%s)",
+ succ->m_src->m_index, succ->m_dest->m_index,
+ succ_desc.get ());
+ }
program_point next_point
= program_point::before_supernode (succ->m_dest, succ,