public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: drizzle drizzle <drizzle76@gmail.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Annotations in tree
Date: Tue, 26 Jul 2005 22:39:00 -0000	[thread overview]
Message-ID: <7326d8e4050726153954b9a5f0@mail.gmail.com> (raw)
In-Reply-To: <20050726203123.GA4355@topo.toronto.redhat.com>

I am not sure if I unerstand ...can you elaborate please ? So what  I
need is if I identify say a reference a[i] inside a loop, I want to
identify the corresponding RTL. What I find now is that
these get transformed for example 
             D.1065_17 = a_matrix[i_24][k_30];   // I have identified this 
             sum_12 = D.1065_17 + sum_31;

gets coalesced back into 
            sum = a_matrix[i][k] + sum;  before it is expaned into rtl.. 
How do I keep track that it is indeed the same array reference though
it has gone through some transformation. ( One another tranformation
is generating a pointer to it instead of using the array).

Sumesh 


On 7/26/05, Diego Novillo <dnovillo@redhat.com> wrote:
> On Tue, Jul 26, 2005 at 04:21:51PM -0400, drizzle drizzle wrote:
> 
> >    I am trying to find out how to insert annotations for certain array
> > references identified in tree-loop-linear.c so that when converting to
> >
> In the ARRAY_REFs themselves?  I would build a hash table on the
> side.  If it's on the DECLs, you could use var_ann() to add
> annotations.
>

  reply	other threads:[~2005-07-26 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 20:21 drizzle drizzle
2005-07-26 20:31 ` Diego Novillo
2005-07-26 22:39   ` drizzle drizzle [this message]
2005-07-26 23:10     ` Daniel Berlin
2005-07-26 23:43       ` drizzle drizzle
2005-07-26 23:54         ` Daniel Berlin
2005-07-27  0:08           ` drizzle drizzle
2005-07-27  0:21             ` Daniel Berlin

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=7326d8e4050726153954b9a5f0@mail.gmail.com \
    --to=drizzle76@gmail.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@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).