This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: [plugins] Branch for plugins development created
- From: "Grigori Fursin" <grigori dot fursin at inria dot fr>
- To: "'Diego Novillo'" <dnovillo at google dot com>, <gcc at gcc dot gnu dot org>
- Cc: "'Sean Callanan'" <spyffe at cs dot sunysb dot edu>, "'Taras Glek'" <tglek at mozilla dot com>, "'Le-Chun Wu'" <lcwu at google dot com>, "'Basile STARYNKEVITCH'" <basile at starynkevitch dot net>, "'Gerald Pfeifer'" <gerald at pfeifer dot com>, "'Cupertino Miranda'" <cupertinomiranda at gmail dot com>, "'Zbigniew Chamski'" <zbigniew dot chamski at gmail dot com>
- Date: Mon, 9 Feb 2009 00:04:19 +0100
- Subject: RE: [plugins] Branch for plugins development created
- References: <b798aad50902061249o5bb3b83dr8edbd1381f997633@mail.gmail.com>
Hi Diego, et al,
As Sebastian mentioned INRIA finally signed copyright transfer form
for FSF last year so our patches can be easily integrated into GCC.
During this week, I will check the current GCC plugins branch and will send you more
info about the current version of Interactive Compilation Interface
to see how we can help with the developments and what we can reuse
for the GCC plugins (we are naturally interested to test and extend this branch
to simplify further ICI developments). I am working with Zbigniew Chamski and
Cupertino Miranda to extend ICI so I put them in CC.
The current version of ICI is actually synchronized with the latest GCC trunk,
has a very small code-base and touches minimal parts of the compiler -
it have been used in various projects
within last 5-6 months to select optimization passes or change their orders
per function to optimize performance/code-size for programs and Linux libraries
at ARC, IBM and STMicro or test the new local releases of a compiler and instrument
program for further analysis. I need to look through all the feedback we got
from our users to update the Plugins Wiki with the practical
usage scenarios and different plugins we developed - I will try to
do it within next few days and will check the proposed GCC plugins API
to sync with ICI...
Take care and have a good week,
Grigori
> -----Original Message-----
> From: Diego Novillo [mailto:dnovillo@google.com]
> Sent: Friday, February 06, 2009 9:49 PM
> To: gcc@gcc.gnu.org
> Cc: Sean Callanan; Taras Glek; Le-Chun Wu; Basile STARYNKEVITCH; Grigori Fursin; Gerald
> Pfeifer
> Subject: [plugins] Branch for plugins development created
>
> I have created the plugins branch (rev. 143989). As I offered before,
> I will help maintain the branch synchronized with mainline and with
> patch reviews. The branch can be checked out with
>
> $ svn co svn://gcc.gnu.org/svn/gcc/branches/plugins
>
> As usual, I created a wiki page for the branch
> (http://gcc.gnu.org/wiki/plugins) and patched svn.html to document the
> branch.
>
> Before I can accept patches, however, I need to make sure that
> everyone has copyright assignments on file. I know that Taras, Basile
> and Le-Chun do. Sean and Grigori, do you folks have copyright papers
> already?
>
> I understand that Le-Chun has an initial patch for the branch based on
> the API we've been discussing. If everyone agrees, I will review that
> for inclusion.
>
> Gerald, is this patch to svn.html OK? I see that there are some stale
> entries in there. I'll clean them up with a follow-up patch.
>
>
> Thanks. Diego.
>
> Index: htdocs/svn.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
> retrieving revision 1.109
> diff -d -u -p -r1.109 svn.html
> --- htdocs/svn.html 9 Dec 2008 15:27:03 -0000 1.109
> +++ htdocs/svn.html 6 Feb 2009 20:40:35 -0000
> @@ -391,6 +391,11 @@ the command <code>svn log --stop-on-copy
> DWARF-4 is currently under development, so changes on this branch
> will remain experimental until Version 4 is officially finalized.</dd>
>
> + <dt>plugins</dt>
> + <dd>This branch adds plugin functionality to GCC. See the <a
> + href="http://gcc.gnu.org/wiki/plugins">plugins wiki</a> for
> + details.</dd>
> +
> </dl>
>
> <h4>Architecture-specific</h4>