On Mon, 2012-09-10 at 13:54 +0200, Michael Matz wrote:
> Hi,
> 
> On Mon, 10 Sep 2012, Richard Guenther wrote:
> 
> > > Thoughts?
> > 
> > Micha was also working on the proposed introspection API, I blame him 
> > for not posting anything about this despite it's being "ready" since a 
> > few months...
> 
> He.  I didn't yet come to make the changes about operand inspectors since 
> your last comments, so it's again unready :-)

Micha: I'm very interested in seeing your code.

Is it possible for you to post your work-in-progress code somewhere?

I know that you don't feel it's ready for committing, but I would find
it helpful - I'm interested in understanding the general approach,
rather than seeing completeness or perfection.  In particular, as the
maintainer of the gcc-python-plugin I want something that will make my
life easier.  By that I mean: something that will make it easier to keep
my plugin compatible against "as many gcc versions as possible" (which
currently means 4.6 and 4.7, but I want to add 4.8 and so on), and
minimize the amount of recompiling I have to do over ABI issues within a
GCC release.  My plugin is currently implemented in C (requiring C++
would be a pain for me, but would be doable, I think).

Hope this makes sense - thanks!
Dave

Reply via email to