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/99956] loop interchange fails when altering bwaves inner loop Date: Mon, 26 Apr 2021 11:58:34 +0000 [thread overview] Message-ID: <bug-99956-4-Szkn9CrPCJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99956 --- Comment #4 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:6ff66d1ea48960fe96bb51a750c01135e65fe452 commit r12-125-g6ff66d1ea48960fe96bb51a750c01135e65fe452 Author: Richard Biener <rguenther@suse.de> Date: Wed Apr 7 14:53:40 2021 +0200 tree-optimization/99956 - improve loop interchange When we apply store motion and DSE manually to the bwaves kernel in gfortran.dg/pr81303.f loop interchange no longer happens because the perfect nest considered covers outer loops we cannot analyze strides for. The following compensates for this by shrinking the nest in this analysis which was already possible but on a too coarse granularity. It shares the shrinked nest with the rest of the DRs so the complexity overhead should be negligible. 2021-04-07 Richard Biener <rguenther@suse.de> PR tree-optimization/99956 * gimple-loop-interchange.cc (compute_access_stride): Try instantiating the access in a shallower loop nest if instantiating failed. (compute_access_strides): Pass adjustable loop_nest to compute_access_stride. * gfortran.dg/pr99956.f: New testcase.
next prev parent reply other threads:[~2021-04-26 11:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-07 12:21 [Bug tree-optimization/99956] New: " rguenth at gcc dot gnu.org 2021-04-07 12:28 ` [Bug tree-optimization/99956] " rguenth at gcc dot gnu.org 2021-04-07 12:29 ` rguenth at gcc dot gnu.org 2021-04-07 12:46 ` rguenth at gcc dot gnu.org 2021-04-07 12:57 ` rguenth at gcc dot gnu.org 2021-04-26 11:58 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-26 11:59 ` 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-99956-4-Szkn9CrPCJ@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).