public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Debug counter for IVOPTs
Date: Fri, 08 Nov 2019 13:15:00 -0000	[thread overview]
Message-ID: <nycvar.YFH.7.76.1911081415310.5566@zhemvz.fhfr.qr> (raw)


Bootstrapped / tested on x86_64-unknwon-linux-gnu, applied.

Richard.

2019-11-08  Richard Biener  <rguenther@suse.de>

	* dbgcnt.def (ivopts_loop): Add.
	* tree-ssa-loop-ivopts.c (tree_ssa_iv_optimize): Check
	ivopts_loop before optimizing a loop.

Index: gcc/dbgcnt.def
===================================================================
--- gcc/dbgcnt.def	(revision 277965)
+++ gcc/dbgcnt.def	(working copy)
@@ -199,3 +199,4 @@ DEBUG_COUNTER (dom_unreachable_edges)
 DEBUG_COUNTER (match)
 DEBUG_COUNTER (store_merging)
 DEBUG_COUNTER (gimple_unroll)
+DEBUG_COUNTER (ivopts_loop)
Index: gcc/tree-ssa-loop-ivopts.c
===================================================================
--- gcc/tree-ssa-loop-ivopts.c	(revision 277965)
+++ gcc/tree-ssa-loop-ivopts.c	(working copy)
@@ -131,6 +131,7 @@ along with GCC; see the file COPYING3.
 #include "tree-ssa-address.h"
 #include "builtins.h"
 #include "tree-vectorizer.h"
+#include "dbgcnt.h"
 
 /* FIXME: Expressions are expanded to RTL in this pass to determine the
    cost of different addressing modes.  This should be moved to a TBD
@@ -8043,6 +8044,9 @@ tree_ssa_iv_optimize (void)
   /* Optimize the loops starting with the innermost ones.  */
   FOR_EACH_LOOP (loop, LI_FROM_INNERMOST)
     {
+      if (!dbg_cnt (ivopts_loop))
+	continue;
+
       if (dump_file && (dump_flags & TDF_DETAILS))
 	flow_loop_dump (loop, dump_file, NULL, 1);
 

                 reply	other threads:[~2019-11-08 13:15 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=nycvar.YFH.7.76.1911081415310.5566@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --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).