public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/66706] Redundant bitmask instruction on x >> (n & 32) Date: Tue, 30 Jun 2015 16:20:00 -0000 [thread overview] Message-ID: <bug-66706-4-Axcl7gR4ji@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66706-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66706 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2015-06-30 Assignee|unassigned at gcc dot gnu.org |segher at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> --- For some reason when combining the zero_extend with the lshiftrt, combine writes it as the equivalent and-of-subreg. Which doesn't match any existing backend pattern. Confirmed; mine.
next prev parent reply other threads:[~2015-06-30 16:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 15:49 [Bug rtl-optimization/66706] New: Redundant shift " msebor at gcc dot gnu.org 2015-06-30 16:20 ` segher at gcc dot gnu.org [this message] 2015-07-02 16:27 ` [Bug rtl-optimization/66706] Redundant bitmask " segher at gcc dot gnu.org 2015-07-02 16:30 ` segher at gcc dot gnu.org 2015-07-03 14:38 ` segher at gcc dot gnu.org 2020-10-21 3:15 ` guojiufu 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-66706-4-Axcl7gR4ji@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: 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).