🚀 go-pugleaf

We have tageted gcc to produce a 3-addr intermediate representation
that we then use as input to a parallelizing compiler for VLIW
architectures.  Unfortunately, we lose some source-level information
with this technique that could be useful to us.  In particular,
for each LOAD and STORE produced by gcc, I would like to know
why that memory reference was produced:

    o  Is it for an explicit reference in the source (e.g. an array
       reference)?  If so, then what is the source-level identifier
       being referenced? (I can get type information, etc. from debugging
       information produced in the 3-addr code).

    o  Or is it for spill code and/or argument passing?  What is the
       source-level identifier (if any)?

It seems like getting this information should simply be a matter of
passing the information from the TREE representation to the RTL
representation and then finally to the 3-addr target code, but I
don't know much about the internals of gcc, and am hoping that
one of you experts out there will be able to give me some hints
on how I can do this.

Thanks in advance!

Steve Novack
Dept. of ICS
Univ. of California
Irvine, CA  92717

office: (714) 725-2248
email: snovack@ics.uci.edu