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 tree-optimization/107451] [11 Regression] Segmentation fault with vectorized code since r11-6434 Date: Tue, 02 May 2023 12:03:38 +0000 [thread overview] Message-ID: <bug-107451-4-paqFDWUu45@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107451-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:e74518e28d98994c2059063f339533d344db85e0 commit r11-10673-ge74518e28d98994c2059063f339533d344db85e0 Author: Richard Biener <rguenther@suse.de> Date: Thu Dec 22 09:36:17 2022 +0100 tree-optimization/107451 - SLP load vectorization issue When vectorizing SLP loads with permutations we can access excess elements when the load vector type is bigger than the group size and the vectorization factor covers less groups than necessary to fill it. Since we know the code will only access up to group_size * VF elements in the unpermuted vector we can simply fill the rest of the vector with whatever we want. For simplicity this patch chooses to repeat the last group. PR tree-optimization/107451 * tree-vect-stmts.c (vectorizable_load): Avoid loading SLP group members from group numbers in excess of the vectorization factor. * gcc.dg/torture/pr107451.c: New testcase. (cherry picked from commit 7b2cf5041460859ca4f58e5da1308b7ef9129d8b)
next prev parent reply other threads:[~2023-05-02 12:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-28 19:07 [Bug tree-optimization/107451] New: Segmentation fault with vectorized code bartoldeman at users dot sourceforge.net 2022-10-28 19:19 ` [Bug tree-optimization/107451] " jakub at gcc dot gnu.org 2022-10-28 19:19 ` [Bug tree-optimization/107451] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-10-29 0:12 ` bartoldeman at users dot sourceforge.net 2022-10-31 3:29 ` crazylht at gmail dot com 2022-11-05 10:21 ` rguenth at gcc dot gnu.org 2022-11-05 10:29 ` [Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434 jakub at gcc dot gnu.org 2022-11-17 9:06 ` rguenth at gcc dot gnu.org 2022-11-17 14:48 ` rguenth at gcc dot gnu.org 2022-11-17 14:57 ` bartoldeman at users dot sourceforge.net 2022-11-17 14:58 ` rguenth at gcc dot gnu.org 2022-12-22 11:21 ` cvs-commit at gcc dot gnu.org 2022-12-22 11:21 ` [Bug tree-optimization/107451] [11/12 " rguenth at gcc dot gnu.org 2023-03-15 9:47 ` cvs-commit at gcc dot gnu.org 2023-05-02 12:03 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-02 12:05 ` [Bug tree-optimization/107451] [11 " 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-107451-4-paqFDWUu45@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).