This is the mail archive of the
mailing list for the GCC project.
Re: instrumentation injection & trees
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: jason at sourcelabs dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 3 Mar 2005 18:28:07 -0500
- Subject: Re: instrumentation injection & trees
- References: <email@example.com>
On Mar 3, 2005, at 6:12 PM, firstname.lastname@example.org wrote:
I'm new to the gcc community. I've been asked to modify gcc to allow
to inject various kinds of instrumentation during compilation. My
plan is to capture the tree being generated by the front end, augment
and pass it on to the back end. It seems like a reasonable approach
can't find much information about interpreting and manipulating trees.
Does anyone have any information about this technique of wedging code
between the front and back ends, or, better yet, some examples? Is
a better approach? Are there existing tools that might eliminate the
to write this instrumentation injector from scratch?
If you are going this for 4.0.0 and above, you might want to
look into gimplify_function_tree and the code for