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/98167] [x86] Failure to optimize operation on indentically shuffled operands into a shuffle of the result of the operation
Date: Fri, 27 Aug 2021 01:13:08 +0000 [thread overview]
Message-ID: <bug-98167-4-ExS6fN5KqV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98167-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98167
--- Comment #14 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Hongtao.liu from comment #13)
> fold shulfps to vec_perm_exp, but still 2 shulfps are generated.
>
> __m128 f (__m128 a, __m128 b)
> {
> vector(4) float _3;
> vector(4) float _5;
> vector(4) float _6;
>
> ;; basic block 2, loop depth 0
> ;; pred: ENTRY
> _3 = VEC_PERM_EXPR <b_2(D), b_2(D), { 0, 0, 0, 0 }>;
> _5 = VEC_PERM_EXPR <a_4(D), a_4(D), { 0, 0, 0, 0 }>;
> _6 = _3 * _5;
> return _6;
> ;; succ: EXIT
>
> }
So this is a bit more complex as not all targets have a good extract/dup
functionary for scalars. So maybe this should be done as a define_insn for x86.
next prev parent reply other threads:[~2021-08-27 1:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 2:09 [Bug target/98167] New: [x86] Failure to optimize operation on indentically shuffled operand " gabravier at gmail dot com
2020-12-07 2:12 ` [Bug target/98167] [x86] Failure to optimize operation on indentically shuffled operands " gabravier at gmail dot com
2020-12-07 8:04 ` rguenth at gcc dot gnu.org
2020-12-07 12:19 ` crazylht at gmail dot com
2020-12-07 12:26 ` rguenth at gcc dot gnu.org
2020-12-07 12:39 ` rguenth at gcc dot gnu.org
2020-12-07 12:40 ` rguenth at gcc dot gnu.org
2020-12-07 12:43 ` rguenth at gcc dot gnu.org
2020-12-08 23:05 ` glisse at gcc dot gnu.org
2020-12-10 5:49 ` crazylht at gmail dot com
2021-01-14 10:45 ` crazylht at gmail dot com
2021-01-14 10:59 ` jakub at gcc dot gnu.org
2021-08-27 0:51 ` cvs-commit at gcc dot gnu.org
2021-08-27 0:58 ` crazylht at gmail dot com
2021-08-27 1:13 ` pinskia at gcc dot gnu.org [this message]
2021-08-27 5:48 ` crazylht at gmail dot com
2021-08-27 6:31 ` crazylht at gmail dot com
2021-08-27 6:48 ` pinskia at gcc dot gnu.org
2021-08-27 7:02 ` crazylht at gmail dot com
2021-08-27 7:39 ` pinskia at gcc dot gnu.org
2022-01-11 11:27 ` rguenth at gcc dot gnu.org
2022-11-15 5:36 ` cvs-commit 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-98167-4-ExS6fN5KqV@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).