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/101009] [10/11/12 Regression] wrong code with "-O3 -fno-tree-sra" Date: Fri, 11 Jun 2021 09:26:20 +0000 [thread overview] Message-ID: <bug-101009-4-5foHXnq5Qo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101009 --- Comment #11 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:336c41dbcb21740f8964021e157bc69ca547059b commit r12-1381-g336c41dbcb21740f8964021e157bc69ca547059b Author: Richard Biener <rguenther@suse.de> Date: Fri Jun 11 09:33:58 2021 +0200 middle-end/101009 - fix distance vector recording This fixes recording of distance vectors in case the DDR has just constant equal indexes. In that case we expect distance vectors with zero distances to be recorded which is what was done when any distance was computed for affine indexes. 2021-06-11 Richard Biener <rguenther@suse.de> PR middle-end/101009 * tree-data-ref.c (build_classic_dist_vector_1): Make sure to set *init_b to true when we encounter a constant equal index pair. (compute_affine_dependence): Also dump the actual DR_REF. * gcc.dg/torture/pr101009.c: New testcase.
next prev parent reply other threads:[~2021-06-11 9:26 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 8:17 [Bug tree-optimization/101009] New: " suochenyao at 163 dot com 2021-06-10 9:28 ` [Bug tree-optimization/101009] [12 Regression] " rguenth at gcc dot gnu.org 2021-06-10 9:40 ` rguenth at gcc dot gnu.org 2021-06-10 13:38 ` jakub at gcc dot gnu.org 2021-06-11 6:08 ` rguenth at gcc dot gnu.org 2021-06-11 6:23 ` rguenth at gcc dot gnu.org 2021-06-11 6:41 ` rguenth at gcc dot gnu.org 2021-06-11 7:19 ` rguenth at gcc dot gnu.org 2021-06-11 7:21 ` [Bug tree-optimization/101009] [10/11/12 " rguenth at gcc dot gnu.org 2021-06-11 7:33 ` rguenth at gcc dot gnu.org 2021-06-11 9:15 ` jakub at gcc dot gnu.org 2021-06-11 9:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-11 9:27 ` [Bug tree-optimization/101009] [10/11 " rguenth at gcc dot gnu.org 2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org 2021-09-06 10:18 ` [Bug tree-optimization/101009] [10 " cvs-commit at gcc dot gnu.org 2021-09-06 10:18 ` 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-101009-4-5foHXnq5Qo@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).