From: "Sebastian Pop" <sebpop@gmail.com>
To: "Alexander Monakov" <amonakov@gmail.com>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: Fix for data deps classical distance vector
Date: Sun, 29 Jul 2007 13:29:00 -0000 [thread overview]
Message-ID: <cb9d34b20707290408j19cf4a99n6507cd6faac7ee1c@mail.gmail.com> (raw)
In-Reply-To: <cb9d34b20707290407j1dc228d1hbed05671313969dd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
On 7/29/07, Sebastian Pop <sebpop@gmail.com> wrote:
> Hi,
>
> I've just committed to trunk the attached patch. It should fix the ICE
> that you saw when trying to represent non integer distance vectors.
> The patch passed bootstrap and test on amd64-linux.
>
> Sebastian
>
[-- Attachment #2: 785_self_dr.diff --]
[-- Type: text/x-diff, Size: 998 bytes --]
* tree-data-ref.c (add_multivariate_self_dist): Parametric access
functions cannot be represented as classical distance vectors.
Index: gcc/tree-data-ref.c
===================================================================
--- gcc/tree-data-ref.c (revision 126917)
+++ gcc/tree-data-ref.c (working copy)
@@ -2810,10 +2810,14 @@ add_multivariate_self_dist (struct data_
lambda_vector dist_v;
int v1, v2, cd;
- /* Polynomials with more than 2 variables are not handled yet. */
- if (TREE_CODE (c_0) != INTEGER_CST)
+ /* Polynomials with more than 2 variables are not handled yet. When
+ the evolution steps are parameters, it is not possible to
+ represent the dependence using classical distance vectors. */
+ if (TREE_CODE (c_0) != INTEGER_CST
+ || TREE_CODE (CHREC_RIGHT (c_1)) != INTEGER_CST
+ || TREE_CODE (CHREC_RIGHT (c_2)) != INTEGER_CST)
{
- DDR_ARE_DEPENDENT (ddr) = chrec_dont_know;
+ DDR_AFFINE_P (ddr) = false;
return;
}
prev parent reply other threads:[~2007-07-29 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 11:08 Sebastian Pop
2007-07-29 13:29 ` Sebastian Pop [this message]
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=cb9d34b20707290408j19cf4a99n6507cd6faac7ee1c@mail.gmail.com \
--to=sebpop@gmail.com \
--cc=amonakov@gmail.com \
--cc=gcc-patches@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).