linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: garritfra <garritfranke@gmail.com>
To: luc.vanoostenryck@gmail.com, linux-sparse@vger.kernel.org
Cc: garritfra <garritfranke@gmail.com>
Subject: [PATCH] ir-validate: remove orphan comments
Date: Thu, 18 Jun 2020 16:09:14 +0200	[thread overview]
Message-ID: <20200618140913.25321-1-garritfranke@gmail.com> (raw)

Please let me know if these comments have a right to be there, but I
think they are orphans and can be removed.

Signed-off-by: Garrit Franke <garritfranke@gmail.com>
---
 optimize.c | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/optimize.c b/optimize.c
index e8cb7fc3..31d94e61 100644
--- a/optimize.c
+++ b/optimize.c
@@ -75,7 +75,6 @@ repeat:
 	 */
 	do {
 		simplify_memops(ep);
-		//ir_validate(ep);
 		do {
 			repeat_phase = 0;
 			clean_up_insns(ep);
@@ -86,15 +85,11 @@ repeat:
 
 			if (repeat_phase & REPEAT_SYMBOL_CLEANUP)
 				simplify_memops(ep);
-			//ir_validate(ep);
 		} while (repeat_phase);
 		pack_basic_blocks(ep);
-		//ir_validate(ep);
 		if (repeat_phase & REPEAT_CFG_CLEANUP)
 			kill_unreachable_bbs(ep);
-		//ir_validate(ep);
 	} while (repeat_phase);
-	//ir_validate(ep);
 
 	vrfy_flow(ep);
 
@@ -111,13 +106,11 @@ repeat:
 	 * again
 	 */
 	if (simplify_flow(ep)) {
-		//ir_validate(ep);
 		clear_liveness(ep);
 		if (repeat_phase & REPEAT_CFG_CLEANUP)
 			kill_unreachable_bbs(ep);
 		goto repeat;
 	}
-	//ir_validate(ep);
 
 	/* Finally, add deathnotes to pseudos now that we have them */
 	if (dbg_dead)
-- 
2.25.1

             reply	other threads:[~2020-06-18 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 14:09 garritfra [this message]
2020-06-18 18:58 ` [PATCH] ir-validate: remove orphan comments Luc Van Oostenryck

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=20200618140913.25321-1-garritfranke@gmail.com \
    --to=garritfranke@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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 NNTP newsgroup(s).