public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30318]  New: VRP does not create ANIT_RANGEs on overflow
Date: Thu, 28 Dec 2006 13:28:00 -0000	[thread overview]
Message-ID: <bug-30318-10053@http.gcc.gnu.org/bugzilla/> (raw)

VRP should, if overfow is defined, create anti-ranges if plus or minus
cause wrapping.

void test2 (unsigned int i)
{
  if (i <= 0x0fffffffa)
    {
      return;
    }
  if (i == 0x0ffffffff)
    {
      return;
    }
  {
    unsigned int v = i + 2;
    {
      if (v != 0)
        {
          if (v != 0x0ffffffff)
            {
              link_error ();
            }
        }
    }
  }
}

we should be able to optimize this.  So [UINT_MAX-4, UINT_MAX-1] + 2
is ~[1, UINT_MAX-1].

(I have a patch)


-- 
           Summary: VRP does not create ANIT_RANGEs on overflow
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
        AssignedTo: rguenth at gcc dot gnu dot org
        ReportedBy: rguenth at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30318


             reply	other threads:[~2006-12-28 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 13:28 rguenth at gcc dot gnu dot org [this message]
2006-12-28 19:35 ` [Bug tree-optimization/30318] VRP does not create ANTI_RANGEs " rguenth at gcc dot gnu dot org
2006-12-28 20:33 ` rguenth at gcc dot gnu dot 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-30318-10053@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).