On Tue, 2012-09-11 at 11:17 +0200, Richard Guenther wrote:
Sorry for the belated response; various comments inline throughout...
> On Tue, Sep 11, 2012 at 3:10 AM, David Malcolm wrote:
> > On Mon, 2012-09-10 at 17:20 +0200, Michael Matz wrote:
> >> Hi David,
> >>
> >> On Mon, 10 Sep 2012, David
e changed again (ABI wise) in the future,
>
> Sounds good.
>
>>
>> > My plugin is currently implemented in C (requiring C++ would be a pain
>> > for me, but would be doable, I think).
>>
>> ... and the API C only, yes, definitely.
>>
>> I hope th
ccessors, never to be changed again (ABI wise) in the future,
Sounds good.
>
> > My plugin is currently implemented in C (requiring C++ would be a pain
> > for me, but would be doable, I think).
>
> ... and the API C only, yes, definitely.
>
> I hope the above made
Hi David,
On Mon, 10 Sep 2012, David Malcolm wrote:
> Is it possible for you to post your work-in-progress code somewhere?
Attached.
> 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 seei
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 month
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
itten in C?
>
> It's still a work-in-progress, but can be seen here:
>
> http://git.fedorahosted.org/cgit/gcc-python-plugin.git/tree/gcc-c-api?h=proposed-plugin-api
>
> i.e. within the "proposed-plugin-api" branch of the gcc-python-plugin,
> within the "gcc-c
ere:
http://git.fedorahosted.org/cgit/gcc-python-plugin.git/tree/gcc-c-api?h=proposed-plugin-api
i.e. within the "proposed-plugin-api" branch of the gcc-python-plugin,
within the "gcc-c-api" subdirectory. I've been gradually porting the
python plugin to use the proposed API, rather
