public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/kubaneko/heads/histogram)] Add -fuse-histogram-in-peeling
Date: Sat, 22 Apr 2023 10:50:10 +0000 (GMT)	[thread overview]
Message-ID: <20230422105010.E8B8B3858CDB@sourceware.org> (raw)

https://gcc.gnu.org/g:54eac3378042a6543e03a2dd75673b6e1d67f5da

commit 54eac3378042a6543e03a2dd75673b6e1d67f5da
Author: Honza <jh@ryzen3.suse.cz>
Date:   Sat Apr 22 12:49:51 2023 +0200

    Add -fuse-histogram-in-peeling

Diff:
---
 gcc/common.opt               | 4 ++++
 gcc/tree-ssa-loop-ivcanon.cc | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gcc/common.opt b/gcc/common.opt
index 50bcc523fd2..e4ef0685484 100644
--- a/gcc/common.opt
+++ b/gcc/common.opt
@@ -2291,6 +2291,10 @@ fpeel-loops
 Common Var(flag_peel_loops) Optimization
 Perform loop peeling.
 
+fuse-histograms-in-peeling
+Common Var(flag_use_histogram_in_peeling) Init(1) Optimization
+Use histograms in loop peelings.
+
 fpeephole
 Common Var(flag_no_peephole,0) Optimization
 Enable machine specific peephole optimizations.
diff --git a/gcc/tree-ssa-loop-ivcanon.cc b/gcc/tree-ssa-loop-ivcanon.cc
index 6a9ed49bb25..d5a10bb5aff 100644
--- a/gcc/tree-ssa-loop-ivcanon.cc
+++ b/gcc/tree-ssa-loop-ivcanon.cc
@@ -1102,7 +1102,7 @@ try_peel_loop (class loop *loop,
   auto_vec<int> good_peels;
   auto_vec<int> prcnt;
   prcnt.safe_push (0);
-  bool histogram_peeling = loop->counters != NULL;
+  bool histogram_peeling = flag_use_histogram_in_peeling && (loop->counters != NULL);
   if (!loop->counters && loop->header->count.reliable_p ()
       && loop->header->count.nonzero_p ()
       && dump_enabled_p ())

                 reply	other threads:[~2023-04-22 10:50 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=20230422105010.E8B8B3858CDB@sourceware.org \
    --to=hubicka@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: 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).