Quoting Ian Lance Taylor <i...@google.com>:
Joern Rennecke <amyl...@spamcop.net> writes:
Combining the runtime Library with Independent Modules is certainly
more specific than combining the runtime Library with Independent Modules
and anything else you feel like.
Moreover, a typical link will contain Target Code which has not been
generated by Eligible Compilation Processes - including any object file
which has been assembled from assembly Source Code, like crt0.S or
strcmp.S, will disqualify the work for the exception.
We simply disagree on this point. I won't repeat myself again.
So, assuming you may link in other stuff that is not an Independent
Module, that logically includes pieces derived from gcc itself if you
make sure that they either don't need the GCC runtime, or that they
incorporate pieces of it. You'd only need to make sure that you
compile these with an Eligible Compilation Process.
So, you could mechanically change each gcc source file to incorporate
a bit of libgcc (using new function names so that it doesn't change
behaviour) thus rendering it not an Independent Module, bootstrap the
compiler, and convey the binary under terms of your choice.
I don't think that the FSF really intends such an interpretation.
