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/97770] New: Missing vectorization for vpopcnt Date: Tue, 10 Nov 2020 02:12:22 +0000 [thread overview] Message-ID: <bug-97770-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770 Bug ID: 97770 Summary: Missing vectorization for vpopcnt Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: crazylht at gmail dot com Target Milestone: --- cat test.c --- void foo(int* __restrict dest, int* src, int n) { for (int i = 0; i != 8; i++) dest[i] = __builtin_popcount (src[i]); } --- gcc -O3 -march=icelake-server -S -fopt-info-all Inlined 0 calls, eliminated 0 functions test.c:4:3: missed: couldn't vectorize loop test.c:5:15: missed: not vectorized: relevant stmt not supported: _7 = __builtin_popcount (_5); test.c:2:1: note: vectorized 0 loops in function. test.c:4:3: note: ***** Analysis failed with vector mode VOID test.c:4:3: note: ***** Analysis failed with vector mode V8SI test.c:4:3: note: ***** Skipping vector mode V32QI, which would repeat the analysis for V8SI test.c:6:1: note: ***** Analysis failed with vector mode VOID This loop could be vectorized by ICC and Clang: foo(int*, int*, int): vpopcntd ymm0, YMMWORD PTR [rsi] #5.15 vmovdqu YMMWORD PTR [rdi], ymm0 #5.5 vzeroupper #6.1 ret
next reply other threads:[~2020-11-10 2:12 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 2:12 crazylht at gmail dot com [this message] 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 ` [Bug tree-optimization/97770] [ICELAKE]suboptimal vectorization for vpopcntw/b/q rguenther at suse dot de 2021-06-10 18:32 ` 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@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: linkBe 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).