public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3332] Improve path_range_query dumps. Date: Fri, 3 Sep 2021 13:31:50 +0000 (GMT) [thread overview] Message-ID: <20210903133150.A1954384A07D@sourceware.org> (raw) https://gcc.gnu.org/g:134289146468b0b7215159d1940a674e1c3b228e commit r12-3332-g134289146468b0b7215159d1940a674e1c3b228e Author: Aldy Hernandez <aldyh@redhat.com> Date: Fri Sep 3 11:13:16 2021 +0200 Improve path_range_query dumps. Tested on x86-64 Linux. gcc/ChangeLog: * gimple-range-path.cc (path_range_query::dump): Dump path length. (path_range_query::precompute_ranges): Dump entire path. Diff: --- gcc/gimple-range-path.cc | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/gcc/gimple-range-path.cc b/gcc/gimple-range-path.cc index 77b823e7bd5..6d6e5eb6635 100644 --- a/gcc/gimple-range-path.cc +++ b/gcc/gimple-range-path.cc @@ -92,7 +92,7 @@ path_range_query::dump (FILE *dump_file) bitmap_iterator bi; extern void dump_ranger (FILE *, const vec<basic_block> &); - fprintf (dump_file, "Path is:\n"); + fprintf (dump_file, "Path is (length=%d):\n", m_path->length ()); dump_ranger (dump_file, *m_path); fprintf (dump_file, "Imports:\n"); @@ -315,7 +315,17 @@ path_range_query::precompute_ranges (const vec<basic_block> &path, m_imports = imports; if (DEBUG_SOLVER) - fprintf (dump_file, "path_range_query: precompute_ranges\n"); + { + fprintf (dump_file, "\npath_range_query: precompute_ranges for path: "); + for (unsigned i = path.length (); i > 0; --i) + { + basic_block bb = path[i - 1]; + fprintf (dump_file, "BB %d", bb->index); + if (i > 1) + fprintf (dump_file, ", "); + } + fprintf (dump_file, "\n"); + } while (1) {
reply other threads:[~2021-09-03 13:31 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=20210903133150.A1954384A07D@sourceware.org \ --to=aldyh@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).