[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses gcc-exception-faq.html
|
From: |
Yavor Doganov |
|
Subject: |
www/licenses gcc-exception-faq.html |
|
Date: |
Wed, 28 Jan 2009 13:10:14 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 09/01/28 13:10:14
Modified files:
licenses : gcc-exception-faq.html
Log message:
Use prettier quotation marks like the rest of the articles.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gcc-exception-faq.html?cvsroot=www&r1=1.3&r2=1.4
Patches:
Index: gcc-exception-faq.html
===================================================================
RCS file: /web/www/www/licenses/gcc-exception-faq.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gcc-exception-faq.html 27 Jan 2009 20:34:13 -0000 1.3
+++ gcc-exception-faq.html 28 Jan 2009 13:10:03 -0000 1.4
@@ -74,7 +74,7 @@
sure that they're addressed. Below we've addressed specific concerns
that we expect users will have. If you have questions about the new
exception that aren't mentioned here, please feel free to contact us
-at <a href="mailto:address@hidden";>address@hidden</a>.</p>
+at <a href="mailto:address@hidden";><address@hidden></a>.</p>
<h3>How the Exception Works</h3>
@@ -97,8 +97,8 @@
terms relate to common scenarios.</p>
<p>When you write your software, it consists of a set of source code
-files. Each file is an "Independent Module," as long as it doesn't
-contain any source from the GCC libraries.</p>
+files. Each file is an “Independent Module,” as long as
+it doesn't contain any source from the GCC libraries.</p>
<p>When you compile those source code files, they usually go through a
series of steps: source code generation, preprocessing, compilation to
@@ -108,23 +108,24 @@
will go through the process of compiling high-level code into some
low-level language such as assembly code or Java bytecode. This phase
is when GCC combines or links your own code with code from the GCC
-libraries. We call it the "Compilation Process." The output you get
-from it is called "Target Code," as long as that output is not used as
-compiler intermediate representation, or to create such an
-intermediate representation.</p>
-
-<p>In order to take advantage of this permission, the Compilation Process
-that you use to create Target Code has to be "Eligible," which means
-that it does not involve both GCC and GPL-incompatible software. It's
-important to remember that the Compilation Process starts when you
-feed <em>any</em> high-level code to GCC, and ends as soon as it generates
-anything that can be considered Target Code. Because of that, as long
-as GCC isn't writing out intermediate representation, your Compilation
-Process can still be Eligible even if you use GCC in conjunction with
-GPL-incompatible assemblers, linkers, or high-level source generators:
-those programs aren't involved in the Compilation Process as it's
-defined here. The only place you can't use GPL-incompatible software
-with GCC is when it's performing the core compilation work.</p>
+libraries. We call it the “Compilation Process.” The
+output you get from it is called “Target Code,” as long as
+that output is not used as compiler intermediate representation, or to
+create such an intermediate representation.</p>
+
+<p>In order to take advantage of this permission, the Compilation
+Process that you use to create Target Code has to be
+“Eligible,” which means that it does not involve both GCC
+and GPL-incompatible software. It's important to remember that the
+Compilation Process starts when you feed <em>any</em> high-level code
+to GCC, and ends as soon as it generates anything that can be
+considered Target Code. Because of that, as long as GCC isn't writing
+out intermediate representation, your Compilation Process can still be
+Eligible even if you use GCC in conjunction with GPL-incompatible
+assemblers, linkers, or high-level source generators: those programs
+aren't involved in the Compilation Process as it's defined here. The
+only place you can't use GPL-incompatible software with GCC is when
+it's performing the core compilation work.</p>
<p>So, if you use GCC, with or without GPL-compatible enhancements, that
would be an Eligible Compilation Process. If you only use
@@ -139,7 +140,7 @@
<p>As long as you use an Eligible Compilation Process, then you have
permission to take the Target Code that GCC generates and propagate it
-"under terms of your choice."</p>
+“under terms of your choice.”</p>
<p>If you did use GPL-incompatible software in conjunction with GCC
during the Compilation Process, you would not be able to take
@@ -156,10 +157,11 @@
FSF, or with my operating system) to compile GPL-incompatible
software. How does this change affect me?</dt>
-<dd><p>It should not affect you at all. Unless you've configured GCC to
-output intermediate representation—which is rare—the new exception
is
-designed to ensure that you have no license obligations when you do
-this, just as the old exceptions were.</p></dd>
+<dd><p>It should not affect you at all. Unless you've configured GCC
+to output intermediate representation—which is rare—the
+new exception is designed to ensure that you have no license
+obligations when you do this, just as the old exceptions
+were.</p></dd>
<dt>Who does this change affect?</dt>
@@ -174,23 +176,23 @@
generators to compile my program. Can I still take advantage of the
exception?</dt>
-<dd><p>Yes. The Compilation Process can start with any "code entirely
-represented in a high-level, non-intermediate language." This
-includes code generated by a preprocessor or other proprietary
-software. As such, the Compilation Process in this case does not
-involve any proprietary software; it qualifies as Eligible, and the
-exception is available for this program.</p></dd>
+<dd><p>Yes. The Compilation Process can start with any “code
+entirely represented in a high-level, non-intermediate
+language.” This includes code generated by a preprocessor or
+other proprietary software. As such, the Compilation Process in this
+case does not involve any proprietary software; it qualifies as
+Eligible, and the exception is available for this program.</p></dd>
<dt>I use GCC in conjunction with proprietary assemblers and/or linkers to
compile my program. Can I still take advantage of the exception?</dt>
<dd><p>Yes. The Compilation Process ends when the compiler generates
-Target Code, which includes output that is "suitable for input to an
-assembler, loader, linker and/or execution phase." In other words,
-the Compilation Process in this case is over when you have assembly
-code or unlinked object files from GCC, and so it does not involve any
-proprietary software. It qualifies as Eligible, and the exception is
-thus available for this program.</p></dd>
+Target Code, which includes output that is “suitable for input
+to an assembler, loader, linker and/or execution phase.” In
+other words, the Compilation Process in this case is over when you
+have assembly code or unlinked object files from GCC, and so it does
+not involve any proprietary software. It qualifies as Eligible, and
+the exception is thus available for this program.</p></dd>
<dt>I use GCC to compile parts of my program, and a proprietary
compiler to compile other parts. The pieces are combined afterward,
@@ -203,7 +205,7 @@
for this program.</p></dd>
<dt>Why is compiler intermediate representation excluded from the
-definition of "Target Code?"</dt>
+definition of “Target Code?”</dt>
<dd><p>When we first considered adding a plugin infrastructure to GCC, we
were deeply concerned about the possibility that someone would write a