public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <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: Fri, 29 Mar 2013 11:03:00 -0000 [thread overview]
Message-ID: <bug-14741-4-pNGTLgMbdU@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
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2006-04-23 17:57:20 |2013-03-29
CC| |Joost.VandeVondele at mat
| |dot ethz.ch
Blocks| |51119
Summary|missing transformations |graphite with loop blocking
|lead to poorly optimized |and interchanging doesn't
|code |optimize a matrix
| |multiplication loop
Known to fail|tree-ssa |4.9.0
--- Comment #17 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2013-03-29 11:03:40 UTC ---
With 4.9 trunk using
gfortran -ffast-math -O3 -march=native -fgraphite -floop-interchange
-floop-block PR14741.f90
The testcase still runs about 8x slower than what ifort produces at -O3 -xHost.
This is too bad, and in my opinion blocks as simple solution for PR51119
next parent reply other threads:[~2013-03-29 11:03 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 [this message]
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
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-pNGTLgMbdU@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: link
Be 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).