public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101846] Improve __builtin_shufflevector emitted code
Date: Wed, 15 Dec 2021 03:25:42 +0000 [thread overview]
Message-ID: <bug-101846-4-xYTqKzjtW5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101846-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101846
--- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Andrew Pinski from comment #7)
> With just -mavx512f we produce a bunch of instructions (looking like we went
> to scalar mode) while LLVM is able to produce:
> foo(short __vector(16)): # @foo(short __vector(16))
> .cfi_startproc
> # %bb.0:
> vpmovzxwd ymm1, xmm0 # ymm1 =
> xmm0[0],zero,xmm0[1],zero,xmm0[2],zero,xmm0[3],zero,xmm0[4],zero,xmm0[5],
> zero,xmm0[6],zero,xmm0[7],zero
> vextracti128 xmm0, ymm0, 1
> vpmovzxwd ymm0, xmm0 # ymm0 =
> xmm0[0],zero,xmm0[1],zero,xmm0[2],zero,xmm0[3],zero,xmm0[4],zero,xmm0[5],
> zero,xmm0[6],zero,xmm0[7],zero
> vinserti64x4 zmm0, zmm1, ymm0, 1
> ret
>
>
zero_extend from ymm to zmm is supported under avx512bw, LLVM breaks them into
2 zero extends from xmm to ymm, and then pack them back to zmm.
next prev parent reply other threads:[~2021-12-15 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 13:14 [Bug target/101846] New: " jakub at gcc dot gnu.org
2021-08-10 14:30 ` [Bug target/101846] " rguenth at gcc dot gnu.org
2021-08-11 3:35 ` crazylht at gmail dot com
2021-08-12 1:53 ` crazylht at gmail dot com
2021-08-12 1:55 ` crazylht at gmail dot com
2021-08-12 6:03 ` cvs-commit at gcc dot gnu.org
2021-08-16 7:30 ` cvs-commit at gcc dot gnu.org
2021-12-15 1:50 ` pinskia at gcc dot gnu.org
2021-12-15 1:52 ` pinskia at gcc dot gnu.org
2021-12-15 3:25 ` crazylht at gmail dot com [this message]
2021-12-15 11:26 ` jakub 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-101846-4-xYTqKzjtW5@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).