This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [plugins] [patch] Initial implementation of GCC plugin support


Hi all,
Actually, in may be out of the current plugins scope, but we may eventually 
need to call plugins in all compilation stages, i.e. cc1, linking, etc.
We can use exactly the same invocation mechanism in all cases and just provide
a feature to tell the plugin where it is called from (that's how we deal with
that in ICI at the moment) ...
Cheers,
Grigori


> -----Original Message-----
> From: Joseph Myers [mailto:joseph@codesourcery.com]
> Sent: Tuesday, February 24, 2009 2:50 PM
> To: Basile STARYNKEVITCH
> Cc: Le-Chun Wu; gcc-patches@gcc.gnu.org; Diego Novillo; Taras Glek; Grigori Fursin; Zbigniew
> Chamski; Sean Callanan; Cupertino Miranda
> Subject: Re: [plugins] [patch] Initial implementation of GCC plugin support
> 
> On Tue, 24 Feb 2009, Basile STARYNKEVITCH wrote:
> 
> > In my perception, plugin should be loaded & initialized before any source file
> > is compiled. In particular, I see a possible need for plugins to be loaded &
> > used without any source file compiled:
> 
> gcc -fplugin=whatever --version needs to output plugin version strings
> (probably calling cc1 with appropriate options to make it load plugins and
> output their versions).  Likewise --help, with plugin bug reporting
> addresses.
> 
> --
> Joseph S. Myers
> joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]