public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spop at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/32075] can't determine dependence between p->a[x+i] and p->a[x+i+1] where x is invariant but defined in the function Date: Wed, 20 Jun 2007 16:57:00 -0000 [thread overview] Message-ID: <20070620165750.15542.qmail@sourceware.org> (raw) In-Reply-To: <bug-32075-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from spop at gcc dot gnu dot org 2007-06-20 16:57 ------- Subject: Re: can't determine dependence between p->a[x+i] and p->a[x+i+1] where x is invariant but defined in the function The problem has been introduced in version 124927. @@ -3182,7 +3182,7 @@ access_functions_are_affine_or_constant_ for (i = 0; VEC_iterate (tree, fns, i, t); i++) if (!evolution_function_is_constant_p (t) - && !evolution_function_is_affine_multivariate_p (t)) + && !evolution_function_is_affine_multivariate_p (t, 0)) return false; return true; The problem is that this line is saying that t has to be an affine function with respect to the outermost loop_0. That means {x, +, 1}_2 with x defined in loop_0, will be considered as non affine, just because x is varying in loop_0. So in the above patch, we have to replace all these zeros with some other loop number... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32075
next prev parent reply other threads:[~2007-06-20 16:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-24 21:56 [Bug tree-optimization/32075] New: " pinskia at gcc dot gnu dot org 2007-05-25 1:06 ` [Bug tree-optimization/32075] " pinskia at gcc dot gnu dot org 2007-06-18 11:04 ` dorit at il dot ibm dot com 2007-06-20 16:57 ` spop at gcc dot gnu dot org [this message] 2007-06-20 23:42 ` spop at gcc dot gnu dot org 2007-06-20 23:45 ` spop at gcc dot gnu dot org 2007-06-21 21:05 ` ubizjak at gmail dot com 2007-06-24 4:07 ` pinskia at gcc dot gnu dot 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=20070620165750.15542.qmail@sourceware.org \ --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).