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/108401] gcc defeats vector constant generation with intrinsics
Date: Tue, 17 Jan 2023 05:42:07 +0000 [thread overview]
Message-ID: <bug-108401-4-tMtaY8jfIu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108401-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108401
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
> But, if you're going to improve constant generation, please make it so that
> it can recognize not only the particular pattern described in this bug. More
> importantly, it should recognize the all-ones case (as a single pcmpeq) as a
> starting point. Then it can apply shifts to achieve the final result from
> the all-ones vector - shifts of any width, length or direction, including
> psrldq/pslldq. This would improve generated code in a wider range of cases.
yes, we will try to do that. Generally fold intrinsic into compiler IR helps
performance, and for this case we need to optimize codegen for special
immediate broadcast(all-ones + shift)
prev parent reply other threads:[~2023-01-17 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 0:24 [Bug target/108401] New: " andysem at mail dot ru
2023-01-16 5:06 ` [Bug target/108401] " pinskia at gcc dot gnu.org
2023-01-16 5:23 ` pinskia at gcc dot gnu.org
2023-01-16 5:28 ` crazylht at gmail dot com
2023-01-16 7:00 ` amonakov at gcc dot gnu.org
2023-01-16 7:47 ` rguenth at gcc dot gnu.org
2023-01-16 10:04 ` andysem at mail dot ru
2023-01-16 10:42 ` andysem at mail dot ru
2023-01-17 5:42 ` crazylht at gmail dot com [this message]
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-108401-4-tMtaY8jfIu@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).