public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/101200] Unneeded AND after shift
Date: Thu, 24 Jun 2021 20:37:38 +0000	[thread overview]
Message-ID: <bug-101200-4-tpSYBpFC1I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101200-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|tree-optimization           |rtl-optimization
           Keywords|                            |missed-optimization
           Severity|normal                      |enhancement

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This does not make sense:
Trying 12 -> 14:
   12: {r93:QI=r82:QI 0>>0x4;clobber flags:CC;}
      REG_DEAD r82:QI
      REG_UNUSED flags:CC
   14: {r95:DI=r93:QI#0&0xf;clobber flags:CC;}
      REG_UNUSED flags:CC
      REG_DEAD r93:QI
Failed to match this instruction:
(parallel [
        (set (reg:DI 95 [ a ])
            (zero_extract:DI (subreg:HI (reg:QI 82 [ d.0_1 ]) 0)
                (const_int 4 [0x4])
                (const_int 4 [0x4])))
        (clobber (reg:CC 17 flags))
    ])

How can you have a subreg of HI and then get a zero_extract of DI?

  reply	other threads:[~2021-06-24 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 20:19 [Bug tree-optimization/101200] New: " steinar+gcc at gunderson dot no
2021-06-24 20:37 ` pinskia at gcc dot gnu.org [this message]
2021-06-24 20:45 ` [Bug rtl-optimization/101200] " pinskia at gcc dot gnu.org
2021-06-24 20:50 ` pinskia at gcc dot gnu.org
2021-06-25  9:34 ` [Bug target/101200] " jakub at gcc dot gnu.org
2021-06-25  9:38 ` jakub at gcc dot gnu.org
2021-06-25 10:38 ` steinar+gcc at gunderson dot no
2021-06-29 17:40 ` law 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-101200-4-tpSYBpFC1I@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).