public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Eric Botcazou <ebotcazou@adacore.com>
Subject: [PATCH] Improve debug message
Date: Wed, 28 Nov 2012 19:33:00 -0000	[thread overview]
Message-ID: <20121128193327.GC26585@redhat.com> (raw)

As per Eric's suggestiong, this patch makes one debug message more
clear.  Eric, I know you you pre-approved this, but still I'd
appreciate if you could take a look.  Thanks,

2012-11-28  Marek Polacek  <polacek@redhat.com>

	* cprop.c (bypass_block): Improve debug message.

--- gcc/cprop.c.mp	2012-11-28 16:55:03.520375191 +0100
+++ gcc/cprop.c	2012-11-28 20:29:05.664842945 +0100
@@ -1,6 +1,6 @@
 /* Global constant/copy propagation for RTL.
    Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
-   2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
+   2006, 2007, 2008, 2009, 2010, 2011, 2012 Free Software Foundation, Inc.
 
 This file is part of GCC.
 
@@ -1632,8 +1632,10 @@ bypass_block (basic_block bb, rtx setcc,
 				      "in jump_insn %d equals constant ",
 			   regno, INSN_UID (jump));
 		  print_rtl (dump_file, set->src);
-		  fprintf (dump_file, "\nBypass edge from %d->%d to %d\n",
-			   e->src->index, old_dest->index, dest->index);
+		  fprintf (dump_file, "\n\t     when BB %d is entered from "
+				      "BB %d.  Redirect edge %d->%d to %d.\n",
+			   old_dest->index, e->src->index, e->src->index,
+			   old_dest->index, dest->index);
 		}
 	      change = 1;
 	      removed_p = 1;

	Marek

             reply	other threads:[~2012-11-28 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 19:33 Marek Polacek [this message]
2012-11-28 22:21 ` Eric Botcazou

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=20121128193327.GC26585@redhat.com \
    --to=polacek@redhat.com \
    --cc=ebotcazou@adacore.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).