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] |
there is also a difference in these two scenarios:The concern is the many forms of shim layers that possibly could be written more easily with a plug-in framework.
1. a) Company X writes a modification to GCC to generate special intermediate stuff with format Y.
b) Company X writes propietary back end which can only read format Y stuff written by that modification.
2. Same as 1, except that the GCC project does step a) thus semi-standardizing the output.
TO me it is pretty clear that these are very different situations from a license point of view.
I do exactly point 1 for my (Open Source) C++ exception static analysis tool: http://edoc.sourceforge.net/
Well assuming that your tool is GPL'ed there is no issue and this is not a case of 1 above!
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |