public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97770] [ICELAKE]suboptimal vectorization for vpopcntw/b/q
Date: Thu, 10 Jun 2021 06:48:46 +0000 [thread overview]
Message-ID: <bug-97770-4-DMXHT7Msi2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97770-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770
--- Comment #18 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 10 Jun 2021, crazylht at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770
>
> --- Comment #17 from Hongtao.liu <crazylht at gmail dot com> ---
> (In reply to Richard Biener from comment #16)
> > Changing the signature will not help given we don't want to regress other
> > cases.
> > Instead we have to somehow remove the pro- and demotions with the help of
> > patterns. I think using .POPCOUNT should work there.
>
> I'm thinking of reimplementing _mm_popcnt_u64 with a backend builtin like
> __builtin_ia32_popcountll which is defined as ULONGLONG_FTYPE_ULONGLONG, and
> handle that in TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION.
That's going to work I guess but it will pessimize general optimization
which no longer know this is computing popcount (not sure if the old
version exposed that fact).
next prev parent reply other threads:[~2021-06-10 6:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 2:12 [Bug target/97770] New: Missing vectorization for vpopcnt crazylht at gmail dot com
2020-11-10 2:14 ` [Bug target/97770] " crazylht at gmail dot com
2020-11-10 3:04 ` [Bug target/97770] [ICELAKE]Missing " crazylht at gmail dot com
2020-11-10 3:21 ` crazylht at gmail dot com
2020-11-10 8:12 ` rguenth at gcc dot gnu.org
2020-11-10 8:37 ` crazylht at gmail dot com
2020-11-10 8:55 ` rguenth at gcc dot gnu.org
2020-11-10 9:07 ` tkoenig at gcc dot gnu.org
2020-11-10 10:14 ` ubizjak at gmail dot com
2020-11-12 5:18 ` crazylht at gmail dot com
2020-11-12 7:33 ` rguenth at gcc dot gnu.org
2020-11-12 8:47 ` crazylht at gmail dot com
2020-12-03 2:03 ` cvs-commit at gcc dot gnu.org
2020-12-03 2:04 ` crazylht at gmail dot com
2020-12-03 11:24 ` [Bug tree-optimization/97770] " rguenth at gcc dot gnu.org
2021-06-04 7:41 ` crazylht at gmail dot com
2021-06-07 11:33 ` rguenth at gcc dot gnu.org
2021-06-10 3:29 ` crazylht at gmail dot com
2021-06-10 6:48 ` rguenther at suse dot de [this message]
2021-06-10 18:32 ` [Bug tree-optimization/97770] [ICELAKE]suboptimal vectorization for vpopcntw/b/q hjl.tools at gmail dot com
2021-06-11 7:25 ` rguenth at gcc dot gnu.org
2021-06-22 2:40 ` cvs-commit at gcc dot gnu.org
2021-06-22 2:46 ` crazylht at gmail dot com
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-97770-4-DMXHT7Msi2@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).