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 target/98532] Use load/store pairs for 2-element vector in memory permutes
Date: Fri, 12 May 2023 05:34:38 +0000	[thread overview]
Message-ID: <bug-98532-4-UpocfBEPXc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98532-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|pinskia at gcc dot gnu.org         |unassigned at gcc dot gnu.org
      Known to work|                            |12.1.0
             Status|ASSIGNED                    |NEW

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Starting in GCC 12 we produce:
  vect__1.5_10 = *a_4(D);
  vect__2.6_11 = VEC_PERM_EXPR <vect__1.5_10, vect__1.5_10, { 1, 0 }>;
  *b_6(D) = vect__2.6_11;


        ldr     q0, [x0]
        ext     v0.16b, v0.16b, v0.16b, #8
        str     q0, [x1]

RTL level wise:
Trying 8 -> 9:
    8: r96:V2DI=unspec[r92:V2DI,r92:V2DI,0x1] 237
      REG_DEAD r92:V2DI
    9: [r98:DI]=r96:V2DI
      REG_DEAD r98:DI
      REG_DEAD r96:V2DI
Failed to match this instruction:
(set (mem:V2DI (reg:DI 98) [1 *b_6(D)+0 S16 A128])
    (unspec:V2DI [
            (reg:V2DI 92 [ vect__1.5 ]) repeated x2
            (const_int 1 [0x1])
        ] UNSPEC_EXT))

Trying 7, 8 -> 9:
    7: r92:V2DI=[r97:DI]
      REG_DEAD r97:DI
    8: r96:V2DI=unspec[r92:V2DI,r92:V2DI,0x1] 237
      REG_DEAD r92:V2DI
    9: [r98:DI]=r96:V2DI
      REG_DEAD r98:DI
      REG_DEAD r96:V2DI
Failed to match this instruction:
(set (mem:V2DI (reg:DI 98) [1 *b_6(D)+0 S16 A128])
    (unspec:V2DI [
            (mem:V2DI (reg:DI 97) [1 *a_4(D)+0 S16 A128]) repeated x2
            (const_int 1 [0x1])
        ] UNSPEC_EXT))


Maybe the aarch64 backend could have a pattern that matches the last 7,8 -> 9
combined rtl that then expands into a load pair/store pair with reversed
registers.

  parent reply	other threads:[~2023-05-12  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 14:08 [Bug target/98532] New: " ktkachov at gcc dot gnu.org
2021-01-06  8:43 ` [Bug target/98532] " rguenth at gcc dot gnu.org
2021-02-08  2:32 ` pinskia at gcc dot gnu.org
2021-02-08  4:40 ` pinskia at gcc dot gnu.org
2023-05-12  5:34 ` pinskia at gcc dot gnu.org [this message]
2024-02-27  8:27 ` pinskia 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-98532-4-UpocfBEPXc@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).