[gcc r12-4556] Remove superflous debugging messages from the threading registry.

[gcc r12-4556] Remove superflous debugging messages from the threading registry.

[Aldy Hernandez]

https://gcc.gnu.org/g:8b7f9c40ef42411b6f51b508d41a580d4682069e

commit r12-4556-g8b7f9c40ef42411b6f51b508d41a580d4682069e
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Oct 19 10:26:47 2021 +0200

    Remove superflous debugging messages from the threading registry.
    
    These are some random obvious cleanups to the threading dumps, since
    it seems I'm not the only one looking at dumps these days.
    
    The "just threaded" debugging message is redundant since there's
    already an equivalent "Registering jump thread" message.
    
    The "about to thread" message is actually confusing, because the source
    block doesn't match the IL, since the CFG update is mid-flight.
    
    Tested on x86-64 Linux.
    
    gcc/ChangeLog:
    
            * tree-ssa-threadupdate.c (back_jt_path_registry::adjust_paths_after_duplication):
            Remove superflous debugging message.
            (back_jt_path_registry::duplicate_thread_path): Same.

Diff:
---
 gcc/tree-ssa-threadupdate.c | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c
index 293836cdc53..8e6f043bb44 100644
--- a/gcc/tree-ssa-threadupdate.c
+++ b/gcc/tree-ssa-threadupdate.c
@@ -2295,12 +2295,6 @@ back_jt_path_registry::adjust_paths_after_duplication (unsigned curr_path_num)
 {
   vec<jump_thread_edge *> *curr_path = m_paths[curr_path_num];
 
-  if (dump_file && (dump_flags & TDF_DETAILS))
-    {
-      fprintf (dump_file, "just threaded: ");
-      debug_path (dump_file, curr_path_num);
-    }
-
   /* Iterate through all the other paths and adjust them.  */
   for (unsigned cand_path_num = 0; cand_path_num < m_paths.length (); )
     {
@@ -2409,12 +2403,6 @@ back_jt_path_registry::duplicate_thread_path (edge entry,
   if (!can_copy_bbs_p (region, n_region))
     return false;
 
-  if (dump_file && (dump_flags & TDF_DETAILS))
-    {
-      fprintf (dump_file, "\nabout to thread: ");
-      debug_path (dump_file, current_path_no);
-    }
-
   /* Some sanity checking.  Note that we do not check for all possible
      missuses of the functions.  I.e. if you ask to copy something weird,
      it will work, but the state of structures probably will not be