As a matter of protocol, I know there are several groups that all have
implementations. I bet any one of them would love to have the credit
of having their implementation be the one that got adopted. (I know
ours would! We're academics and would love to claim bragging rights.)
In practice, Diego said that we have "several months" before we need
to integrate. Diego has graciously agreed to review patches; how
about instead of having a single implementation that goes in, we all
pool our development resources and do different portions of a fresh
implementation? We could put up a list of tasks on the Wiki and
assign them to groups, so that everybody has a hand in it.
A possible list of tasks (which could each have a patch to itself) is:
- Modify the GCC link process to use libltdl and libtool -export-dynamic
- Add the custom argument handler
- Implement the callback registration code
- Add hooks at relevant locations in GCC
- Implement the plug-in loading code and plug-in initialization
Sean
On Feb 5, 2009, at 7:14 PM, Le-Chun Wu wrote:
Attached please find the patch of our initial prototype of GCC plugin
support based on the APIs described in the (old) wiki page. I also
attached a sample plugin program (dumb-example.c) that shows how a
plugin uses the APIs.
Sean and Taras (and others),
Diego will be creating a branch for the plugin support soon. I know we
still have some issues that have yet to converge (such as flags for
plugin arguments). But in order to get things moving, what do you
think if we start with this patch and move from there? Or if you have
other patches available that implement the currently proposed APIs,
we can start with those too. Thanks.
Le-chun
