Hello,
> >this seems quite close to what TARGET_MEM_REFs are designed for. IMHO,
> >the best way would be to lower the memory references to TARGET_MEM_REFs
> >(*) just once, sometime quite late in the optimization pipeline (just after
> >loop optimizations, for example), so that high-level optimi
Zdenek Dvorak wrote:
Hello,
In principle, I don't see anything forbidding Zdenek's idea.
Unfortunately, what I avoided to mention is that TARGET_MEM_REF nodes
are also transformed into pointer arithmetics
and the equivalent
INDIRECT_REF memory access... therefore, this is not an option even o
Hello,
> >>In principle, I don't see anything forbidding Zdenek's idea.
> >>Unfortunately, what I avoided to mention is that TARGET_MEM_REF nodes
> >>are also transformed into pointer arithmetics
> >>and the equivalent
> >>INDIRECT_REF memory access... therefore, this is not an option even only
Zdenek Dvorak wrote:
Hello,
you might try turning the references to TARGET_MEM_REFs, and copy the
alias information using copy_ref_info to it. I am not sure how that
would interact with the transformations you want to do, but we do lot
of magic to keep the virtual operands for TARGET_MEM_REFs
Hello,
> >>>you might try turning the references to TARGET_MEM_REFs, and copy the
> >>>alias information using copy_ref_info to it. I am not sure how that
> >>>would interact with the transformations you want to do, but we do lot
> >>>of magic to keep the virtual operands for TARGET_MEM_REFs the
Zdenek Dvorak wrote:
Hello,
you might try turning the references to TARGET_MEM_REFs, and copy the
alias information using copy_ref_info to it. I am not sure how that
would interact with the transformations you want to do, but we do lot
of magic to keep the virtual operands for TARGET_MEM_REFs
Hello,
> >you might try turning the references to TARGET_MEM_REFs, and copy the
> >alias information using copy_ref_info to it. I am not sure how that
> >would interact with the transformations you want to do, but we do lot
> >of magic to keep the virtual operands for TARGET_MEM_REFs the same
> >
On 2/19/07, Zdenek Dvorak <[EMAIL PROTECTED]> wrote:
Hello,
you might try turning the references to TARGET_MEM_REFs, and copy the
alias information using copy_ref_info to it. I am not sure how that
would interact with the transformations you want to do, but we do lot
of magic to keep the vi
Hello,
> For instance, let's consider the following struct definition (taken from
> gcc.dg/struct-alias-1.c):
>
> struct S {
>int a[3];
>int x;
> };
>
> This is the original code in GIMPLE pseudo-C dump representation:
>
> s.x = 0;
> i.0 = i;
> s.a[i.0] = 1;
> D.1416 = s.x;
>
On 2/19/07, Roberto COSTA <[EMAIL PROTECTED]> wrote:
Hello,
I've got a question for experts of alias analysis in GCC.
In the CLI back-end of GCC, there is a CLI-specific pass responsible of
some modifications on GIMPLE that simplify the emission of CIL bytecode
(see http://gcc.gnu.org/projects/c
10 matches
Mail list logo
