public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mircea.namolaru at inria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59121] [4.8/4.9 Regression] endless loop with -O2 -floop-parallelize-all Date: Tue, 25 Mar 2014 17:03:00 -0000 [thread overview] Message-ID: <bug-59121-4-w5v028fYgh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59121-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59121 --- Comment #17 from Mircea Namolaru <mircea.namolaru at inria dot fr> --- Yes, data dependencies computation is expensive in the polyehdral model and it could take considerable time - but it is worrying that in too many cases fails to provide (after a few hours left running, when I stop it) an answer for very simple programs. I will ckeck with the isl people if this is the expected behaviour of the isl_union_map_compute_flow (this is the function where the data dependency computation is stuck) and how (and if) they could help us. Many Fortran programs with loops having no-constants bounds and n-dimensional arrays (n>=3) may be affected by this problem and may work only for small dimensions of the arrays. The problem touches especially Fortran, that uses linearized accesses to multi-dimensional arrays - this creates patterns leading to this problem (in this example we have an array acc of dimension 55,48,49 and the array access acc(j,k,l) is transformed to acc(j + 55*k + 2640*l). I've checked the constraints passed to isl_union_map_compute - see that wrapping is perfromed. But wrapping requires modulo operation, expressed by constraints with existential quantifier that may be harder to solve. By disabling the wrapping, some simple examples that before were stuck in data dependency computation finish immediately. In what measure is wrapping necessary ? - as a side-effect it may increase compilation time (that may be already considerable).
next prev parent reply other threads:[~2014-03-25 17:03 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-13 21:22 [Bug tree-optimization/59121] New: " janus at gcc dot gnu.org 2013-11-13 22:07 ` [Bug tree-optimization/59121] " dominiq at lps dot ens.fr 2013-11-13 22:07 ` dominiq at lps dot ens.fr 2013-11-14 10:09 ` janus at gcc dot gnu.org 2013-11-14 10:25 ` dominiq at lps dot ens.fr 2013-11-14 21:04 ` janus at gcc dot gnu.org 2013-11-14 21:10 ` janus at gcc dot gnu.org 2013-11-14 21:19 ` [Bug tree-optimization/59121] [4.8/4.9 Regression] " janus at gcc dot gnu.org 2013-11-15 9:23 ` rguenth at gcc dot gnu.org 2013-11-17 12:27 ` janus at gcc dot gnu.org 2014-01-17 12:32 ` rguenth at gcc dot gnu.org 2014-01-17 17:16 ` law at redhat dot com 2014-02-03 15:23 ` mircea.namolaru at inria dot fr 2014-03-10 16:35 ` mircea.namolaru at inria dot fr 2014-03-10 16:41 ` law at redhat dot com 2014-03-10 22:19 ` grosser at gcc dot gnu.org 2014-03-25 17:03 ` mircea.namolaru at inria dot fr [this message] 2014-03-25 17:27 ` grosser at gcc dot gnu.org 2014-04-10 22:01 ` mircea.namolaru at inria dot fr 2014-04-11 10:45 ` rguenth at gcc dot gnu.org 2014-05-22 9:05 ` [Bug tree-optimization/59121] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:39 ` [Bug tree-optimization/59121] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:20 ` [Bug tree-optimization/59121] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:08 ` [Bug tree-optimization/59121] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:35 ` jakub at gcc dot gnu.org 2015-10-09 14:58 ` spop at gcc dot gnu.org 2015-10-09 15:00 ` 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-59121-4-w5v028fYgh@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).