collect2.texi: GNU CC -> GCC.

	* doc/collect2.texi: GNU CC -> GCC.
	* doc/headerdirs.texi: GNU CC -> GCC.

From-SVN: r66933

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 54b23920327ce81c6dae9b5ac16b793c9c23e6ea..88d99c13f40f265987fa928124d630faa0611eb0 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2003-05-18  Nathanael Nerode  <neroden@gcc.gnu.org>
+
+       * doc/collect2.texi: GNU CC -> GCC.
+       * doc/headerdirs.texi: GNU CC -> GCC.
+
 2003-05-18  Gabriel Dos Reis <gdr@integrable-solutions.net>
 
        * hashtable.h (struct ht_identifier): Add data member "hash_value".

diff --git a/gcc/doc/collect2.texi b/gcc/doc/collect2.texi
index a3d43b280d122264c796f9b46047331f41576046..c3498c5317c91b41f5c2168d306f67621ade634b 100644 (file)
--- a/gcc/doc/collect2.texi
+++ b/gcc/doc/collect2.texi
@@ -5,7 +5,7 @@
 @node Collect2
 @chapter @code{collect2}
 
-GNU CC uses a utility called @code{collect2} on nearly all systems to arrange
+GCC uses a utility called @code{collect2} on nearly all systems to arrange
 to call various initialization functions at start time.
 
 The program @code{collect2} works by linking the program once and

diff --git a/gcc/doc/headerdirs.texi b/gcc/doc/headerdirs.texi
index beac0ddde2281b501091ee12864e8f9fe4bc3ada..bc7f07f36be178f5c9893d21dab3edcfa66c7e7d 100644 (file)
--- a/gcc/doc/headerdirs.texi
+++ b/gcc/doc/headerdirs.texi
@@ -6,28 +6,27 @@
 @chapter Standard Header File Directories
 
 @code{GCC_INCLUDE_DIR} means the same thing for native and cross.  It is
-where GNU CC stores its private include files, and also where GNU CC
-stores the fixed include files.  A cross compiled GNU CC runs
+where GCC stores its private include files, and also where GCC
+stores the fixed include files.  A cross compiled GCC runs
 @code{fixincludes} on the header files in @file{$(tooldir)/include}.
 (If the cross compilation header files need to be fixed, they must be
-installed before GNU CC is built.  If the cross compilation header files
-are already suitable for ISO C and GNU CC, nothing special need be
-done).
+installed before GCC is built.  If the cross compilation header files
+are already suitable for GCC, nothing special need be done).
 
 @code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross.  It
 is where @command{g++} looks first for header files.  The C++ library
 installs only target independent header files in that directory.
 
-@code{LOCAL_INCLUDE_DIR} is used only by native compilers.  GNU CC
+@code{LOCAL_INCLUDE_DIR} is used only by native compilers.  GCC
 doesn't install anything there.  It is normally
 @file{/usr/local/include}.  This is where local additions to a packaged
 system should place header files.
 
-@code{CROSS_INCLUDE_DIR} is used only by cross compilers.  GNU CC
+@code{CROSS_INCLUDE_DIR} is used only by cross compilers.  GCC
 doesn't install anything there.
 
 @code{TOOL_INCLUDE_DIR} is used for both native and cross compilers.  It
-is the place for other packages to install header files that GNU CC will
+is the place for other packages to install header files that GCC will
 use.  For a cross-compiler, this is the equivalent of
 @file{/usr/include}.  When you build a cross-compiler,
 @code{fixincludes} processes any header files in this directory.