New GCC Runtime Library Exception: amendment proposal

[Joern Rennecke <amylaar at spamcop dot net>]

A file is an "Independent Module" if it is not based on the Runtime
Library, except that it may either require the Runtime Library for  
execution after a Compilation Process, or make use of an interface  
provided by the
Runtime Library.

Definitions of "GCC" and "GPL-compatible sotware as in the original.

"Target Code" refers to output from any compiler for a real or virtual  
target processor architecture, in executable form or suitable for  
input to an assembler, loader, linker and/or execution phase.  
Notwithstanding that, Target Code does not include data in any format  
that is used as a compiler intermediate representation, or used for  
producing a compiler intermediate representation.
Where code written in assembly language is Source Code as defined in GPLv3,
it shall also be considered "Target Code".

The "Compilation Process" transforms code entirely represented in a  
high-level, non-intermediate language into Target Code. Thus, for  
example, use of source code generators and preprocessors need not be  
considered part of the Compilation Process, since the Compilation  
Process can be understood as starting with the output of the  
generators or preprocessors.
Where the Source Code as defined in GPLv3 is not written in a high-level
language, yet not in assembly code, the "Compilation Process" transforms the
code entirely represented in Source Code into Target Code.

Defintion of "Eligible" Compilation process as in original.

1. Grant of Additional Permission.

You have permission to propagate a work of Target Code formed by  
combining the Runtime Library with Independent Modules, even if such  
propagation would otherwise violate the terms of GPLv3, provided that  
all Target Code was eithwe generated by Eligible Compilation  
Processes. You may then convey such a combination under terms of your  
choice, consistent with the licensing of the Independent Modules.