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/110788] Spilling to mask register for GPR vec_duplicate
Date: Thu, 27 Jul 2023 07:09:48 +0000 [thread overview]
Message-ID: <bug-110788-4-kSycGzDHjN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110788-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110788
--- Comment #2 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #1)
> I prefer to add an UNSPEC to vpbroadcastm, don't want to mix gpr and kmask
> too much for vec_duplicate:zero_extend pattern.
And got this:
.L3:
vmovapd b(%rax), %ymm1{%k1}
movl %edx, %esi
subl $4, %edx
movzwl %dx, %ecx
vmulpd %ymm3, %ymm1, %ymm0{%k1}{z}
vmovapd %ymm0, a(%rax){%k1}
vpbroadcastd %ecx, %xmm0
addq $32, %rax
vpcmpud $6, %xmm2, %xmm0, %k1
cmpw $4, %si
ja .L3
vzeroupper
next prev parent reply other threads:[~2023-07-27 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:40 [Bug target/110788] New: " rguenth at gcc dot gnu.org
2023-07-27 7:02 ` [Bug target/110788] " crazylht at gmail dot com
2023-07-27 7:09 ` crazylht at gmail dot com [this message]
2023-07-27 11:29 ` ubizjak at gmail dot com
2023-07-27 13:55 ` crazylht at gmail dot com
2023-07-28 2:07 ` cvs-commit at gcc dot gnu.org
2023-07-28 2:30 ` crazylht at gmail dot com
2023-11-30 10:51 ` liuhongt 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-110788-4-kSycGzDHjN@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).