This is the mail archive of the gcc@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: Defining a common plugin machinery

From: Basile STARYNKEVITCH <basile at starynkevitch dot net>
To: Chris Lattner <clattner at apple dot com>
Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org, Brendon Costa <bcosta at avdat dot com dot au>, Diego Novillo <dnovillo at google dot com>, Sean Callanan <spyffe at cs dot sunysb dot edu>
Date: Sat, 20 Sep 2008 09:13:08 +0200
Subject: Re: Defining a common plugin machinery
References: <48CF93F7.8010901@google.com> <48D2F56B.7060708@avdat.com.au> <48D33A86.4020103@starynkevitch.net> <48D3517C.2010406@avdat.com.au> <48D3BE6F.80103@starynkevitch.net> <48D3C6CD.E117A49E@dessent.net> <48D3DA82.2070306@starynkevitch.net> <m31vzfg4do.fsf@google.com> <70FE60D6-76DE-4C04-8581-970CA2926ACC@apple.com>

Chris Lattner wrote:

Is the plugin machinery intended to eventually allow new (GPL compatible) backends to be used? It would be nice to make llvm-gcc be a plugin.

From what I remember of the plugin BOFS & the Steering Committee Q&A sessions at last GCC summit permitting GPL-ed plugins is one of the intent of plugins.

AFAIK, the concern is -on the opposite of your intents- how to make GPL-ed plugins (legally) easy, and proprietary plugins (legally) impossible, but I am not a lawyer, I know nothing about US law, and I don't know what is happening inside the steering committee or the FSF regarding plugins.

The technical questions about how to make plugin practicals are precisely the scope of the current thread on the gcc@ mailing list.

Regards
--
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

References:
- Defining a common plugin machinery
  - From: Diego Novillo
- Re: Defining a common plugin machinery
  - From: Brendon Costa
- Re: Defining a common plugin machinery
  - From: Basile STARYNKEVITCH
- Re: Defining a common plugin machinery
  - From: Brendon Costa
- Re: Defining a common plugin machinery
  - From: Basile STARYNKEVITCH
- Re: Defining a common plugin machinery
  - From: Brian Dessent
- Re: Defining a common plugin machinery
  - From: Basile STARYNKEVITCH
- Re: Defining a common plugin machinery
  - From: Ian Lance Taylor
- Re: Defining a common plugin machinery
  - From: Chris Lattner

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