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/30317] VRP cannot extract a range from (unsigned int) i + 0x0ffffffff > 4 Date: Sun, 21 Jan 2007 22:44:00 -0000 [thread overview] Message-ID: <20070121224439.2152.qmail@sourceware.org> (raw) In-Reply-To: <bug-30317-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2007-01-21 22:44 ------- Created an attachment (id=12929) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12929&action=view) patch This is what I currently have for this - it fails to bootstrap because it miscompares. A variant without the support for the anti-range tests if (a < 1 || a > 5) aka if ((unsigned)a - 1 > 4) bootstraps and tests ok, but the above adds useful things, so... I guess the hunk in extract_range_from_assert may do the wrong thing in some cases, but I didn't find a testcase for it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30317
next prev parent reply other threads:[~2007-01-21 22:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-28 12:22 [Bug tree-optimization/30317] New: " rguenth at gcc dot gnu dot org 2006-12-28 16:03 ` [Bug tree-optimization/30317] " pinskia at gcc dot gnu dot org 2007-01-20 13:45 ` rguenth at gcc dot gnu dot org 2007-01-21 22:44 ` rguenth at gcc dot gnu dot org [this message] 2007-02-06 10:09 ` rguenth at gcc dot gnu dot org 2008-03-28 12:21 ` rguenth at gcc dot gnu dot org 2008-03-28 12:57 ` rguenth at gcc dot gnu dot org 2009-09-26 18:22 ` pinskia 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=20070121224439.2152.qmail@sourceware.org \ --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: linkBe 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).