🚀 go-pugleaf

In article <1655@racerx.bridge.COM> ken@Bridge.COM (Ken Hardy) writes:
>I'm trying to hack the the C compiler's cc1 module to spit out lots of
>useful (to me) information about structures and/or typedefs that it
>processes.
>
>Can anyone offer me help or _documentation_ on how the compiler uses and
>manages trees or lists or lists of trees or trees of lists?  I've been
>stepping through the compiler code with the debugger and am beginning
>to get a glimmer of what's going on, but I'm lacking the "big
>picture."  Any pointers would be appreciated.
>
>What I'd really like is to find all the typedefs and print out detailed
>info about their base classes, including the components of any
>structures involved.  So when I find a typedef, I need to find what it's
>refering to, and if that is a structure, I need to examine all of it's
>components, and if any of those components are structures (directly or
>thru typedef'ed types), I need to delve into those, recursively.
>
>
>Or maybe I should just sell life insurance.  ;->
>

I recommend looking at dwarfout.c.  In that module, I must traverse the tree
data structure produced by the front-end and output detailed debugging
information based upon those trees.

Dwarfout.c is pretty well documented internally... even if I do say so
myself.

-- 

-- Ronald F. Guilmette ------------------------------------------------------
------ domain address: rfg@netcom.com ---------------------------------------
------ uucp address: ...!uunet!netcom.com!rfg -------------------------------