public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/loop-unswitch-improvement)] Use proper ranges for unswitching candidates.
Date: Mon, 22 Nov 2021 12:44:58 +0000 (GMT)	[thread overview]
Message-ID: <20211122124458.5B2D83858010@sourceware.org> (raw)

https://gcc.gnu.org/g:73024919f386f63e8b12d21b7ea0090d973e31cf

commit 73024919f386f63e8b12d21b7ea0090d973e31cf
Author: Martin Liska <mliska@suse.cz>
Date:   Fri Nov 19 14:13:27 2021 +0100

    Use proper ranges for unswitching candidates.

Diff:
---
 gcc/tree-ssa-loop-unswitch.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/gcc/tree-ssa-loop-unswitch.c b/gcc/tree-ssa-loop-unswitch.c
index 74619ed8b24..e1ff06316e6 100644
--- a/gcc/tree-ssa-loop-unswitch.c
+++ b/gcc/tree-ssa-loop-unswitch.c
@@ -256,7 +256,11 @@ tree_may_unswitch_on (basic_block bb, class loop *loop, gimple_ranger *ranger)
   if (irange::supports_type_p (TREE_TYPE (lhs)))
     {
       ranger->range_on_edge (predicate->true_range, edge_true, lhs);
-      ranger->range_on_edge (predicate->false_range, edge_false, lhs);
+      predicate->false_range = predicate->true_range;
+
+      if (!predicate->false_range.varying_p ()
+	  && !predicate->false_range.undefined_p ())
+	predicate->false_range.invert ();
     }
 
   return predicate;


             reply	other threads:[~2021-11-22 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 12:44 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-19 14:34 Martin Liska
2021-11-19 13:53 Martin Liska

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=20211122124458.5B2D83858010@sourceware.org \
    --to=marxin@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).