On 4/4/07, Daniel Berlin <[EMAIL PROTECTED]> wrote:
On 4/4/07, Zdenek Dvorak <[EMAIL PROTECTED]> wrote:
> Hello,
>
> at the moment, any pass that needs to process memory references are
> complicated (or restricted to handling just a limited set of cases) by
> the need to interpret the quite complex representation of memory
> references that we have in gimple. For example, there are about 1000 of
> lines of quite convoluted code in tree-data-ref.c and about 500 lines in
> tree-ssa-loop-ivopts.c dealing with parsing and analysing memory
> references.
>
> I would like to propose (and possibly also work on implementing) using a
> more uniform representation, described in more details below. The
> proposal is based on the previous discussions
> (http://gcc.gnu.org/ml/gcc/2006-06/msg00295.html) and on what I learned
> about the way memory references are represented in ICC.
> It also subsumes the patches of Daniel to make p[i] (where p is pointer)
> use ARRAY_REFs/MEM_REFs.
>
> I am not sure whether someone does not already work on something
> similar, e.g. with respect to LTO (where the mentioned discussion
> started), or gimple-tuples branch?
I like the idea (though i haven't worked through I agree we want every
component you are describing).
^through whether i agree.
