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/113104] Suboptimal loop-based slp node splicing across iterations Date: Thu, 21 Dec 2023 09:07:53 +0000 [thread overview] Message-ID: <bug-113104-4-4ZbSuPiyYI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113104-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113104 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- See my proposal on the mailing list to lift the restriction of sticking to a single vector size, I think this is another example showing this. If you use BB level vectorization by disabling loop vectorization but not SLP vectorization the code should improve?
next prev parent reply other threads:[~2023-12-21 9:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-21 8:22 [Bug tree-optimization/113104] New: " fxue at os dot amperecomputing.com 2023-12-21 9:07 ` rguenth at gcc dot gnu.org [this message] 2023-12-21 9:33 ` [Bug tree-optimization/113104] " fxue at os dot amperecomputing.com 2023-12-21 9:41 ` rguenther at suse dot de 2023-12-30 12:35 ` rsandifo at gcc dot gnu.org 2024-01-05 16:25 ` cvs-commit at gcc dot gnu.org 2024-01-05 16:32 ` rsandifo at gcc dot gnu.org 2024-01-10 5:01 ` fxue at os dot amperecomputing.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-113104-4-4ZbSuPiyYI@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).