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/110062] missed vectorization in graphicsmagick Date: Wed, 07 Jun 2023 06:43:28 +0000 [thread overview] Message-ID: <bug-110062-4-6vVhaDU7FL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110062-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110062 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- So we fail to vectorize the outer loop (with double reduction) because of t.c:7:25: note: === vect_analyze_data_ref_accesses === t.c:7:25: note: Detected interleaving load _7->red and _7->green t.c:7:25: note: Detected interleaving load _7->red and _7->blue t.c:7:25: note: grouped access in outer loop. t.c:7:25: missed: not vectorized: complicated access pattern. for vectorizing the inner loop SLP discovery fails because of a not grouped load - r[u].{red,green,blue} is handled but k[u] not - I think this is a well-known limitation (that ought to be fixed). We then vectorize the loop with interleaving and peeling for gaps, but profitability says 'width' needs to be 16. We also vectorize the epilog. I suppose the vectorized body isn't entered? Note outer loop vectorization likely isn't profitable even if implemented, so the SLP failure is the thing to fix (which should be easy). Need to find the duplicate bug for this.
next prev parent reply other threads:[~2023-06-07 6:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 13:20 [Bug c/110062] New: " hubicka at gcc dot gnu.org 2023-06-01 9:22 ` [Bug tree-optimization/110062] " crazylht at gmail dot com 2023-06-02 7:33 ` rguenth at gcc dot gnu.org 2023-06-06 20:22 ` hubicka at gcc dot gnu.org 2023-06-07 6:43 ` rguenth at gcc dot gnu.org [this message] 2023-06-07 14:43 ` hubicka at gcc dot gnu.org 2023-06-16 12:23 ` rguenth at gcc dot gnu.org 2023-06-19 2:15 ` crazylht at gmail dot com 2023-06-21 12:01 ` rguenth at gcc dot gnu.org 2023-06-21 12:53 ` rguenth at gcc dot gnu.org 2023-07-31 11:28 ` rguenth at gcc dot gnu.org 2023-11-25 13:33 ` hubicka at gcc dot gnu.org 2023-11-27 7:29 ` 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-110062-4-6vVhaDU7FL@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).