public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/14741] graphite with loop blocking and interchanging doesn't optimize a matrix multiplication loop Date: Sun, 21 Jul 2013 09:59:00 -0000 [thread overview] Message-ID: <bug-14741-4-x89mclLncj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-14741-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14741 --- Comment #22 from Sebastian Pop <spop at gcc dot gnu.org> --- Once we revert that patch, the remaining problem is that graphite_can_represent_scev returns false on this scev: {{(stride.12_14 + offset.13_15) + 1, +, stride.12_14}_1, +, 1}_2 the parameters are defined like this: _12 = *n_11(D); ubound.10_13 = (integer(kind=8)) _12; stride.12_14 = MAX_EXPR <ubound.10_13, 0>; offset.13_15 = ~stride.12_14; #(Data Ref: # bb: 5 # stmt: c__I_lsm.30_8 = *c_21(D)[_20]; # ref: *c_21(D)[_20]; # base_object: *c_21(D); # Access function 0: {{(stride.12_14 + offset.13_15) + 1, +, stride.12_14}_1, +, 1}_2 #) #(Data Ref: # bb: 6 # stmt: _29 = *a_28(D)[_27]; # ref: *a_28(D)[_27]; # base_object: *a_28(D); # Access function 0: {{(stride.12_14 + offset.13_15) + 1, +, 1}_2, +, stride.12_14}_3 #) Why have these arrays been linearized?
next prev parent reply other threads:[~2013-07-21 9:59 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-14741-4@http.gcc.gnu.org/bugzilla/> 2013-03-29 11:03 ` Joost.VandeVondele at mat dot ethz.ch 2013-07-14 7:11 ` spop at gcc dot gnu.org 2013-07-16 2:25 ` spop at gcc dot gnu.org 2013-07-16 2:29 ` spop at gcc dot gnu.org 2013-07-21 9:15 ` spop at gcc dot gnu.org 2013-07-21 9:59 ` spop at gcc dot gnu.org [this message] 2013-07-21 10:14 ` spop at gcc dot gnu.org 2013-07-21 10:34 ` spop at gcc dot gnu.org 2013-07-21 22:01 ` spop at gcc dot gnu.org 2013-07-27 15:19 ` dushistov at mail dot ru 2013-07-27 15:22 ` dushistov at mail dot ru 2013-07-29 22:16 ` spop at gcc dot gnu.org 2014-03-13 15:03 ` spop at gcc dot gnu.org 2014-04-29 12:29 ` dominiq at lps dot ens.fr 2015-05-16 8:48 ` tkoenig at gcc dot gnu.org 2015-05-18 6:28 ` Joost.VandeVondele at mat dot ethz.ch 2015-09-11 9:26 ` manfred99 at gmx dot ch 2015-09-11 19:27 ` spop at gcc dot gnu.org 2015-09-11 21:55 ` dominiq at lps dot ens.fr 2015-09-12 12:06 ` dominiq at lps dot ens.fr 2015-09-12 12:19 ` spop 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-14741-4-x89mclLncj@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).