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/96075] [8/9 Regression] bogus alignment for negative step grouped access Date: Wed, 02 Dec 2020 13:23:26 +0000 [thread overview] Message-ID: <bug-96075-4-hjZDJDULrS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96075-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96075 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:53d76fe758a3e8e0c1f049e75030278427a8fe5d commit r9-9094-g53d76fe758a3e8e0c1f049e75030278427a8fe5d Author: Richard Biener <rguenther@suse.de> Date: Mon Jul 6 16:26:50 2020 +0200 tree-optimization/96075 - fix bogus misalignment calculation This fixes bogus misalignment calculation for negative steps since an assertion a previous comment indicated no longer holds: /* DR_STEP(dr) is the same as -TYPE_SIZE of the scalar type, otherwise we wouldn't be here. */ Thus the following replaces DR_STEP by -TYPE_SIZE. 2020-07-06 Richard Biener <rguenther@suse.de> PR tree-optimization/96075 * tree-vect-data-refs.c (vect_compute_data_ref_alignment): Use TYPE_SIZE_UNIT of the vector component type instead of DR_STEP for the misalignment calculation for negative step. * gcc.dg/vect/slp-46.c: New testcase. (cherry picked from commit dccbf1e2a6e544f71b4a5795f0c79015db019fc3)
next prev parent reply other threads:[~2020-12-02 13:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-06 12:11 [Bug tree-optimization/96075] New: " rguenth at gcc dot gnu.org 2020-07-06 12:16 ` [Bug tree-optimization/96075] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-06 12:39 ` rguenth at gcc dot gnu.org 2020-07-06 13:18 ` rguenth at gcc dot gnu.org 2020-07-06 13:52 ` rsandifo at gcc dot gnu.org 2020-07-06 14:13 ` rguenther at suse dot de 2020-07-06 14:32 ` cvs-commit at gcc dot gnu.org 2020-07-06 14:32 ` [Bug tree-optimization/96075] [8/9/10 " rguenth at gcc dot gnu.org 2020-07-06 14:35 ` rguenth at gcc dot gnu.org 2020-07-07 11:01 ` cvs-commit at gcc dot gnu.org 2020-07-29 9:18 ` [Bug tree-optimization/96075] [8/9 " marxin at gcc dot gnu.org 2020-07-29 9:41 ` rguenth at gcc dot gnu.org 2020-12-02 13:23 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-03 8:54 ` [Bug tree-optimization/96075] [8 " clyon at gcc dot gnu.org 2020-12-03 11:08 ` rguenther at suse dot de 2020-12-03 13:46 ` clyon at gcc dot gnu.org 2020-12-04 10:41 ` cvs-commit at gcc dot gnu.org 2020-12-04 10:41 ` cvs-commit at gcc dot gnu.org 2021-05-14 13:59 ` jakub 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-96075-4-hjZDJDULrS@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).