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 target/60778] shift not folded into shift on x86-64
Date: Mon, 27 Sep 2021 07:59:52 +0000	[thread overview]
Message-ID: <bug-60778-4-ijL6ID51sb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60778-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Trying 7 -> 8:
> >     7: {r87:DI=r89:DI>>0x3;clobber flags:CC;}
> >       REG_DEAD r89:DI
> >       REG_UNUSED flags:CC
> >     8: r88:DF=[r87:DI*0x8+`mem']
> >       REG_DEAD r87:DI
> > Failed to match this instruction:
> > (set (reg:DF 88 [ mem[_1] ])
> >     (mem:DF (plus:DI (and:DI (reg:DI 89)
> >                 (const_int -8 [0xfffffffffffffff8]))
> >             (symbol_ref:DI ("mem") [flags 0x2]  <var_decl 0x7f6b6efd9c60
> > mem>)) [1 mem[_1]+0 S8 A64]))
> > 
> > We have 2->2 combine now but it looks like we don't try to split inside a
> > mem ...
> 
> This address looks similar to how Alpha implemented unaligned load. It looks
> like combine tries to synthesize AND address.

That is from the (x >> 3) * 8.  Perhaps a combine splitter that will tell
combine that it should split it at the AND?  Though, not sure if the cost will
say that it is beneficial.

  parent reply	other threads:[~2021-09-27  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 16:01 [Bug target/60778] New: " sunfish at mozilla dot com
2014-04-08  8:51 ` [Bug target/60778] " rguenth at gcc dot gnu.org
2021-09-26 21:43 ` pinskia at gcc dot gnu.org
2021-09-27  7:46 ` ubizjak at gmail dot com
2021-09-27  7:59 ` jakub at gcc dot gnu.org [this message]
2021-09-27  8:22 ` ubizjak at gmail dot com

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-60778-4-ijL6ID51sb@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).