From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] analyzer: log out-edge description in exploded_graph::process_node
Date: Tue, 19 Jul 2022 10:02:10 -0400 [thread overview]
Message-ID: <20220719140210.1336855-1-dmalcolm@redhat.com> (raw)
I found this logging tweak very helpful when working on
PR analyzer/106284.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-1747-g434d521d118fc7.
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>
---
gcc/analyzer/engine.cc | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc
index 9ffcc410839..4f7f9d03900 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,
--
2.26.3
reply other threads:[~2022-07-19 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220719140210.1336855-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).