On Tue, 21 Jun 2011 14:33:20 -0400 David Malcolm <dmalc...@redhat.com> wrote: > It's still at the "experimental proof-of-concept stage"; expect crashes > and tracebacks (I'm new to the insides of GCC, and I may have > misunderstood things. I'm entirely ignoring the garbage collector, and > I've also used a few entrypoints that aren't yet exposed in the plugin > headers). > > It's already possible to use this to add additional compiler > errors/warnings, e.g. domain-specific checks, or static analysis. > > One of my goals for this is to "teach" GCC about the common mistakes > people make when writing extensions for CPython [1], but it could be > used > - e.g. to teach GCC about GTK's reference-counting semantics, > - to check locking in the Linux kernel > - to check signal-safety in APIs, etc > - rapid prototyping >
For your information, MELT has the same goals, except that it does not ignore the Gcc garbage collector (on the contrary, it is built above it). See http://gcc-melt.org/ for more, or download the MELT branch (or the MELT plugin). Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mine, sont seulement les miennes} ***
