public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wwwhhhyyy333 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112325] New: Missed vectorization after cunrolli Date: Wed, 01 Nov 2023 02:41:20 +0000 [thread overview] Message-ID: <bug-112325-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112325 Bug ID: 112325 Summary: Missed vectorization after cunrolli Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: wwwhhhyyy333 at gmail dot com Target Milestone: --- testcase: #include <stdint.h> #include <string.h> typedef struct { float s; int8_t qs[32]; } block; void foo (const int n, float * restrict s, const int8_t q[4], const block * restrict y) { const int qk = 32; const int nb = n / qk; float sumf = 0.0; int sumi = 0; for (int i = 0; i < nb; i++) { uint32_t qh; memcpy(&qh, q, 4); for (int j = 0; j < qk/2; ++j) { sumi += (qh >> j) * y[i].qs[j]; } sumf += (y[i].s * (float) sumi); } *s = sumf; } This can be vectorized under -O2 -mavx512vl but not -O3 -mavx512vl, see https://godbolt.org/z/csPr4cPen Under -O3 -mavx512vl -fdisable-tree-cunrolli the loop can also be vectorized.
next reply other threads:[~2023-11-01 2:41 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 2:41 wwwhhhyyy333 at gmail dot com [this message] 2023-11-01 2:46 ` [Bug tree-optimization/112325] " pinskia at gcc dot gnu.org 2023-11-02 9:51 ` [Bug tree-optimization/112325] Missed vectorization of reduction after unrolling rguenth at gcc dot gnu.org 2023-11-16 8:03 ` liuhongt at gcc dot gnu.org 2023-11-16 8:15 ` liuhongt at gcc dot gnu.org 2023-11-16 9:15 ` rguenth at gcc dot gnu.org 2023-11-17 6:19 ` pinskia at gcc dot gnu.org 2023-11-17 6:21 ` pinskia at gcc dot gnu.org 2023-11-20 2:52 ` cvs-commit at gcc dot gnu.org 2023-11-21 0:34 ` cvs-commit at gcc dot gnu.org 2024-02-27 6:02 ` liuhongt at gcc dot gnu.org 2024-02-27 6:13 ` liuhongt at gcc dot gnu.org 2024-02-27 7:26 ` liuhongt at gcc dot gnu.org 2024-02-27 7:53 ` rguenther at suse dot de 2024-02-27 7:58 ` rguenther at suse dot de 2024-02-28 7:26 ` liuhongt at gcc dot gnu.org 2024-02-28 8:23 ` rguenther at suse dot de 2024-02-28 8:26 ` 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-112325-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).