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/102789] libgomp.c++/simd-3.C fails after r12-4340 for 32 bits Date: Mon, 08 Nov 2021 05:31:45 +0000 [thread overview] Message-ID: <bug-102789-4-1NFKqyemMH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102789-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:6cce26752d8431a1ef6d3f9a97fa0ee2e9f96816 commit r9-9815-g6cce26752d8431a1ef6d3f9a97fa0ee2e9f96816 Author: Kewen Lin <linkw@linux.ibm.com> Date: Mon Oct 25 21:05:02 2021 -0500 vect: Don't update inits for simd_lane_access DRs [PR102789] As PR102789 shows, when vectorizer does some peelings for alignment in prologues, function vect_update_inits_of_drs would update the inits of some drs. But as the failed case, we shouldn't update the dr for simd_lane_access, it has the fixed-length storage mainly for the main loop, the update can make the access out of bound and access the unexpected element. gcc/ChangeLog: PR tree-optimization/102789 * tree-vect-loop-manip.c (vect_update_inits_of_drs): Do not update inits of simd_lane_access. (cherry picked from commit f3dbd3f36d55178d0a9e4431043cbc950524969a)
next prev parent reply other threads:[~2021-11-08 5:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 20:09 [Bug libgomp/102789] New: [12 regression] libgomp.c++/simd-3.C fails after r12-xxxx " seurer at gcc dot gnu.org 2021-10-15 20:10 ` [Bug libgomp/102789] " seurer at gcc dot gnu.org 2021-10-18 6:29 ` [Bug libgomp/102789] [12 regression] libgomp.c++/simd-3.C fails after r12-4340 " rguenth at gcc dot gnu.org 2021-10-18 10:05 ` [Bug target/102789] " jakub at gcc dot gnu.org 2021-10-18 10:20 ` jakub at gcc dot gnu.org 2021-10-19 6:51 ` linkw at gcc dot gnu.org 2021-10-20 6:24 ` linkw at gcc dot gnu.org 2021-10-25 3:08 ` linkw at gcc dot gnu.org 2021-10-26 3:18 ` cvs-commit at gcc dot gnu.org 2021-10-26 3:21 ` [Bug tree-optimization/102789] " linkw at gcc dot gnu.org 2021-10-26 3:28 ` linkw at gcc dot gnu.org 2021-11-05 13:57 ` [Bug tree-optimization/102789] " rguenth at gcc dot gnu.org 2021-11-05 14:00 ` jakub at gcc dot gnu.org 2021-11-08 5:31 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-08 5:33 ` cvs-commit at gcc dot gnu.org 2021-11-08 5:34 ` cvs-commit at gcc dot gnu.org 2021-11-08 5:36 ` linkw 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-102789-4-1NFKqyemMH@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).