On Tue, Feb 2, 2016 at 4:23 PM, David Edelsohn <dje....@gmail.com> wrote: > On Tue, Feb 2, 2016 at 5:03 PM, H.J. Lu <hjl.to...@gmail.com> wrote: >> On Tue, Feb 2, 2016 at 1:35 PM, Cary Coutant <ccout...@gmail.com> wrote: >>>> include/plugin-api.h defines an ABI between linker and compiler, >>>> which can be used to implement linker plug-in by any compilers. >>>> I'd like to add GCC Runtime Library Exception to include/plugin-api.h >>>> so that the linker plug-in can have non-GPL licenses. >>> >>> This is OK with me. >>> >>> -cary >> >> Here is a patch. OK for trunk? > > You have not explained why this actually is needed and only the FSF > can agree to license changes. >
Here is an example of linker plugin without using GCC: https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=ld/testplug.c;h=cec947c51c44e7e4334036ecfe96392eb7c32643;hb=HEAD I'd like to put such plugin under a non-GPL license. As I understand, Cary, as the contributor of include/plugin-api.h, may release it under a different license. Of course, changing license of include/plugin-api.h in GCC source tree may need FSF approval. Should we ask FSF to get an approval? -- H.J.
