public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Wed, 06 Jan 2021 08:43:34 +0000	[thread overview]
Message-ID: <bug-98532-4-lVwnmqavZy@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

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
  _1 = BIT_FIELD_REF <*a_4(D), 64, 64>;
  _2 = BIT_FIELD_REF <*a_4(D), 64, 0>;
  tmp_5 = {_1, _2};

note this is another case where we'd like to improve forwprop to canonicalize
this to

  _1 = *a_4(D);
  tmp_5 = VEC_PERM <_1, _1, { 1, 0 }>;

which is more "SSA friendly".  That would lead to what clang generates
I guess (and be maybe easier to combine from to ldp/stp).

  reply	other threads:[~2021-01-06  8:43 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 ` rguenth at gcc dot gnu.org [this message]
2021-02-08  2:32 ` [Bug target/98532] " 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
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-lVwnmqavZy@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).