Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-12 Thread Ludovic Courtès
Hi, (Sorry for the delay.) I suppose the proposed API doesn’t cover all the needs of your Python bindings and their applications, does it? How do you plan to export the GIMPLE and tree.h APIs? Regarding iterators, there are things like: GCC_IMPLEMENT_PUBLIC_API(bool) gcc_cfg_for_each_block

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-04 Thread Richard Guenther
On Tue, Apr 3, 2012 at 6:02 PM, David Malcolm wrote: > On Tue, 2012-04-03 at 15:23 +0200, Richard Guenther wrote: >> On Tue, Apr 3, 2012 at 12:03 PM, Richard Guenther >> wrote: >> > On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: >> >> I wrote a script and ported my proposed API for GCC plu

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-04 Thread Richard Guenther
On Tue, Apr 3, 2012 at 8:15 PM, Romain Geissler wrote: > > Le 3 avr. 2012 à 18:02, David Malcolm a écrit : > >> On Tue, 2012-04-03 at 15:23 +0200, Richard Guenther wrote: >>> On Tue, Apr 3, 2012 at 12:03 PM, Richard Guenther >>> wrote: On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: >>

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-03 Thread Romain Geissler
Le 3 avr. 2012 à 18:02, David Malcolm a écrit : > On Tue, 2012-04-03 at 15:23 +0200, Richard Guenther wrote: >> On Tue, Apr 3, 2012 at 12:03 PM, Richard Guenther >> wrote: >>> On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: I wrote a script and ported my proposed API for GCC plugins f

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-03 Thread David Malcolm
On Tue, 2012-04-03 at 15:23 +0200, Richard Guenther wrote: > On Tue, Apr 3, 2012 at 12:03 PM, Richard Guenther > wrote: > > On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: > >> I wrote a script and ported my proposed API for GCC plugins from my > >> CamelCase naming convention to an undersco

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-03 Thread David Malcolm
On Tue, 2012-04-03 at 12:03 +0200, Richard Guenther wrote: > On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: > > I wrote a script and ported my proposed API for GCC plugins from my > > CamelCase naming convention to an underscore_based_convention (and > > manually fixed up things in a few pla

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-03 Thread Richard Guenther
On Tue, Apr 3, 2012 at 12:03 PM, Richard Guenther wrote: > On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: >> I wrote a script and ported my proposed API for GCC plugins from my >> CamelCase naming convention to an underscore_based_convention (and >> manually fixed up things in a few places

Re: Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-03 Thread Richard Guenther
On Mon, Apr 2, 2012 at 7:21 PM, David Malcolm wrote: > I wrote a script and ported my proposed API for GCC plugins from my > CamelCase naming convention to an underscore_based_convention (and > manually fixed up things in a few places also). > > The result compiles and passes the full test suite f

Proposed gcc plugin plugin API mk 2 (this time without camel case!)

2012-04-02 Thread David Malcolm
I wrote a script and ported my proposed API for GCC plugins from my CamelCase naming convention to an underscore_based_convention (and manually fixed up things in a few places also). The result compiles and passes the full test suite for the Python plugin; that said, I'm still breaking the encapsu