This is the mail archive of the
mailing list for the GCC project.
Re: GCC Plug-in Framework ready to port
- From: Diego Novillo <dnovillo at google dot com>
- To: Sean Callanan <spyffe at cs dot sunysb dot edu>, Taras Glek <tglek at mozilla dot com>, Basile STARYNKEVITCH <basile at starynkevitch dot net>, Grigori Fursin <grigori dot fursin at inria dot fr>, Le-Chun Wu <lcwu at google dot com>, Brendon Costa <bcosta at avdat dot com dot au>, Emmanuel Fleury <fleury at labri dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 31 Jan 2009 08:11:23 -0500
- Subject: Re: GCC Plug-in Framework ready to port
- References: <firstname.lastname@example.org> <EFC35277-A978-4B6E-9F06-DC56C1409B99@cs.sunysb.edu>
On Fri, Jan 30, 2009 at 23:01, Sean Callanan <email@example.com> wrote:
> We've been off the ML for some time, but we're still out there.
> Is this something that is wanted, or have we been overtaken
> by events and should be porting to someone else's
Thanks for raising the issue. The last time we discussed this
issue (http://gcc.gnu.org/ml/gcc/2008-09/msg00292.html), we did
not reach a final decision, but now that the licensing issues
have been clarified I think it's time we created a branch for
I understand that there are several branches or patchsets for the
various approaches. We clearly need to converge into a single
one. My proposal is:
1- Agree on a common API and document it in
2- Create a new branch to implement that common API. The branch
would *only* be for basic plugin functionality.
3- Decide whether there are plugins that we would want to have in
the standard distribution. I suspect that we will just want 1
or 2 basic applications as examples. Or perhaps, plugins
that are so universally useful for GCC development or users
that we decide to include them.
I offer to create and maintain the new branch, help with patch
reviews and merge it into trunk at the next stage 1.
As Richard said, there is still time (several months), and I
don't think the patches needed to implement the basic plugin
harness are going to be all that large. However, it is important
that we agree on an API so that every group can easily port their
plugins to it.