public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106081] missed vectorization Date: Wed, 26 Jul 2023 13:28:11 +0000 [thread overview] Message-ID: <bug-106081-4-oYaOnxvi3T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106081-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106081 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:5d09fb683a8abce49dc0992f5102aa0189f8f632 commit r14-2790-g5d09fb683a8abce49dc0992f5102aa0189f8f632 Author: Richard Biener <rguenther@suse.de> Date: Wed Jul 26 13:31:16 2023 +0200 tree-optimization/106081 - elide redundant permute The following patch makes sure to elide a redundant permute that can be merged with existing splats represented as load permutations as we now do for non-grouped SLP loads. This is the last bit missing to fix this PR where the main fix was already done by r14-2117-gdd86a5a69cbda4 PR tree-optimization/106081 * tree-vect-slp.cc (vect_optimize_slp_pass::start_choosing_layouts): Assign layout -1 to splats. * gcc.dg/vect/pr106081.c: New testcase.
next prev parent reply other threads:[~2023-07-26 13:28 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-24 15:56 [Bug middle-end/106081] New: " hubicka at gcc dot gnu.org 2022-06-24 16:14 ` [Bug middle-end/106081] " hubicka at gcc dot gnu.org 2022-06-26 8:08 ` crazylht at gmail dot com 2022-06-27 9:01 ` marxin at gcc dot gnu.org 2022-06-27 10:38 ` rguenth at gcc dot gnu.org 2022-06-27 14:26 ` hubicka at gcc dot gnu.org 2022-10-24 0:14 ` pinskia at gcc dot gnu.org 2023-06-21 13:45 ` rguenth at gcc dot gnu.org 2023-06-27 7:49 ` rguenth at gcc dot gnu.org 2023-06-27 8:13 ` rguenth at gcc dot gnu.org 2023-06-27 9:10 ` rsandifo at gcc dot gnu.org 2023-06-28 12:15 ` hubicka at gcc dot gnu.org 2023-07-26 9:34 ` rguenth at gcc dot gnu.org 2023-07-26 9:35 ` rguenth at gcc dot gnu.org 2023-07-26 10:01 ` rsandifo at gcc dot gnu.org 2023-07-26 10:32 ` rguenth at gcc dot gnu.org 2023-07-26 10:52 ` rguenth at gcc dot gnu.org 2023-07-26 11:00 ` rsandifo at gcc dot gnu.org 2023-07-26 11:15 ` rsandifo at gcc dot gnu.org 2023-07-26 12:15 ` rguenther at suse dot de 2023-07-26 13:28 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-26 13:28 ` 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-106081-4-oYaOnxvi3T@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).