This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
[plugins] Comparison of plugin mechanisms
- From: "Grigori Fursin" <grigori dot fursin at inria dot fr>
- To: "'Diego Novillo'" <dnovillo at google dot com>, "'Basile STARYNKEVITCH'" <basile at starynkevitch dot net>
- Cc: <gcc at gcc dot gnu dot org>, "'Sean Callanan'" <spyffe at cs dot sunysb dot edu>, "'Taras Glek'" <tglek at mozilla dot com>, "'Le-Chun Wu'" <lcwu at google dot com>, "'Gerald Pfeifer'" <gerald at pfeifer dot com>, "'Zbigniew Chamski'" <zbigniew dot chamski at gmail dot com>, "'Cupertino Miranda'" <cupertinomiranda at gmail dot com>
- Date: Fri, 13 Feb 2009 00:25:48 +0100
- Subject: [plugins] Comparison of plugin mechanisms
- References: <b798aad50902061249o5bb3b83dr8edbd1381f997633@mail.gmail.com> <498CA5C1.50505@starynkevitch.net> <b798aad50902061313g16a54a36k63325a3b265dfe22@mail.gmail.com>
Dear all,
Zbigniew and I prepared a page on GCC Wiki comparing several current plugin
mechanisms (some parts should be updated) with some suggestions to move forward:
http://gcc.gnu.org/wiki/GCC_PluginComparison
In case we mixed up or misunderstood something about other plugin
efforts, update this page, please ...
Basically, we currently see 3 complementary categories of GCC plugins, depending
on the nature of the extension: production, experimentation/research, and new pass
integration. Each category naturally calls for slightly different API features.
Considering that there are already communities behind "production" and "experimental" plugins,
we think that it would be better to merge two. We will try to prepare a small patch to support
"experimental" plugins by the beginning of next week. In the mean time, would like to know your
thoughts on that matter and how should we proceed forward !..
Cheers,
Grigori & Zbigniew