public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64322] More optimize opportunity for constant folding
Date: Tue, 16 Dec 2014 10:26:00 -0000	[thread overview]
Message-ID: <bug-64322-4-2cx5ZUl3Fy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64322-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64322

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For VRP I'm thinking of (completely untested):
--- gcc/tree-vrp.c.jj    2014-12-01 14:57:30.000000000 +0100
+++ gcc/tree-vrp.c    2014-12-16 10:17:27.543111649 +0100
@@ -2434,6 +2434,7 @@ extract_range_from_binary_expr_1 (value_
       && code != MAX_EXPR
       && code != PLUS_EXPR
       && code != MINUS_EXPR
+      && code != RSHIFT_EXPR
       && (vr0.type == VR_VARYING
       || vr1.type == VR_VARYING
       || vr0.type != vr1.type
@@ -2948,6 +2949,15 @@ extract_range_from_binary_expr_1 (value_
     {
       if (code == RSHIFT_EXPR)
         {
+          /* Even if vr0 is VARYING or otherwise not usable, we can derive
+         useful ranges just from the shift count.  E.g.
+         x >> 63 for signed 64-bit x is always [-1, 0].  */
+          if (vr0.type != VR_RANGE || symbolic_range_p (&vr0))
+        {
+          vr0.type = type = VR_RANGE;
+          vr0.min = vrp_val_min (expr_type);
+          vr0.max = vrp_val_max (expr_type);
+        }
           extract_range_from_multiplicative_op_1 (vr, code, &vr0, &vr1);
           return;
         }


  parent reply	other threads:[~2014-12-16 10:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 23:01 [Bug tree-optimization/64322] New: " ishiura-compiler at ml dot kwansei.ac.jp
2014-12-16  0:41 ` [Bug tree-optimization/64322] " jakub at gcc dot gnu.org
2014-12-16 10:11 ` rguenth at gcc dot gnu.org
2014-12-16 10:26 ` jakub at gcc dot gnu.org [this message]
2014-12-16 11:50 ` rguenth at gcc dot gnu.org
2014-12-17  9:29 ` jakub at gcc dot gnu.org
2014-12-17 12:36 ` jakub at gcc dot gnu.org
2014-12-17 14:25 ` rguenther at suse dot de
2021-08-19 19:26 ` pinskia at gcc dot gnu.org

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=bug-64322-4-2cx5ZUl3Fy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).