public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96208] non-grouped load can be SLP vectorized for 2-element vectors case Date: Wed, 21 Jun 2023 13:39:47 +0000 [thread overview] Message-ID: <bug-96208-4-Qeas5CtlQn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96208 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-06-21 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Summary|non-power-of-2 group size |non-grouped load can be SLP |can be vectorized for |vectorized for 2-element |2-element vectors case |vectors case Status|UNCONFIRMED |ASSIGNED --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- typedef struct { double m1, m2, m3, m4, m5; } the_struct_t; double bar1 (the_struct_t*); double foo (double* k, unsigned int n, the_struct_t* the_struct) { unsigned int u; the_struct_t result; for (u=0; u < n; u++, k--) { result.m1 += (*k)*the_struct[u].m1; result.m2 += (*k)*the_struct[u].m2; result.m3 += (*k)*the_struct[u].m3; result.m4 += (*k)*the_struct[u].m4; } return bar1 (&result); } This has come up again as part of PR110062
next prev parent reply other threads:[~2023-06-21 13:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-15 15:01 [Bug tree-optimization/96208] New: non-power-of-2 group size can be " dpochepk at gmail dot com 2020-07-17 6:44 ` [Bug tree-optimization/96208] " rguenth at gcc dot gnu.org 2023-06-21 13:39 ` rguenth at gcc dot gnu.org [this message] 2023-06-22 12:51 ` [Bug tree-optimization/96208] non-grouped load can be SLP " rguenth at gcc dot gnu.org 2023-06-27 7:48 ` cvs-commit at gcc dot gnu.org 2023-06-27 7:49 ` 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-96208-4-Qeas5CtlQn@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).