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/52267] a&~N where N has all the bits set up till a specific point can be folded to ((unsigned)a) < N
Date: Tue, 13 Mar 2012 17:58:00 -0000 [thread overview]
Message-ID: <bug-52267-4-UTDeoh3Szy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52267-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52267
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #26867|0 |1
is obsolete| |
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-03-13 17:51:48 UTC ---
Created attachment 26885
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26885
gcc48-pr52267.patch
Updated patch. This now passes the testcases (and has two of them, one that
tests whether we optimize as much as we want, the other that we don't
misoptimize), but I'd still like to write more tests tomorrow.
next prev parent reply other threads:[~2012-03-13 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 3:51 [Bug tree-optimization/52267] New: " pinskia at gcc dot gnu.org
2012-02-16 20:40 ` [Bug tree-optimization/52267] " pinskia at gcc dot gnu.org
2012-03-09 4:15 ` pinskia at gcc dot gnu.org
2012-03-09 17:53 ` jakub at gcc dot gnu.org
2012-03-13 17:58 ` jakub at gcc dot gnu.org [this message]
2012-03-15 10:43 ` jakub at gcc dot gnu.org
2012-03-15 12:15 ` jakub at gcc dot gnu.org
2012-03-22 12:53 ` gjl at gcc dot gnu.org
2013-06-29 16:21 ` amylaar at gcc dot gnu.org
2013-06-29 16:24 ` pinskia at gcc dot gnu.org
2013-06-29 20:08 ` amylaar at gcc dot gnu.org
2013-07-04 16:20 ` amylaar 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-52267-4-UTDeoh3Szy@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).