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/101456] Unnecessary vzeroupper when upper bits of YMM registers already zero
Date: Wed, 16 Feb 2022 04:57:49 +0000 [thread overview]
Message-ID: <bug-101456-4-hkSvcveQd8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101456-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101456
--- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #8)
> It turns out that reading YMM registers with all zero bits needs VZEROUPPER
> on Sandy Bride, Ivy Bridge, Haswell, Broadwell and Alder Lake to avoid
> SSE <-> AVX transition penalty.
We should target tune for r12-2571-g9775e465c1fbfc32656de77c618c61acf5bd905d.
next prev parent reply other threads:[~2022-02-16 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 22:39 [Bug target/101456] New: " hjl.tools at gmail dot com
2021-07-14 22:59 ` [Bug target/101456] " arjan at linux dot intel.com
2021-07-15 0:04 ` hjl.tools at gmail dot com
2021-07-15 0:06 ` hjl.tools at gmail dot com
2021-07-15 14:32 ` hjl.tools at gmail dot com
2021-07-16 12:18 ` hjl.tools at gmail dot com
2021-07-28 14:29 ` cvs-commit at gcc dot gnu.org
2021-07-28 15:02 ` hjl.tools at gmail dot com
2022-02-15 13:42 ` hjl.tools at gmail dot com
2022-02-16 4:57 ` crazylht at gmail dot com [this message]
2022-05-06 8:30 ` jakub at gcc dot gnu.org
2023-05-08 12:22 ` rguenth 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-101456-4-hkSvcveQd8@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).