summaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorneroden <neroden@138bc75d-0d04-0410-961f-82ee72b054a4>2003-05-18 15:52:25 +0000
committerneroden <neroden@138bc75d-0d04-0410-961f-82ee72b054a4>2003-05-18 15:52:25 +0000
commit7a7a955b6c5ef5e47ea32271b34dc08d844b0af6 (patch)
tree7c8ee99cb86a9417df0efadbaf0fdffdd2e0911f /gcc/doc
parent6f4f34a7fa6e4d54d09c7c80b1897e7cb5376356 (diff)
downloadgcc-7a7a955b6c5ef5e47ea32271b34dc08d844b0af6.tar.gz
* doc/collect2.texi: GNU CC -> GCC.
* doc/headerdirs.texi: GNU CC -> GCC. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@66933 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/collect2.texi2
-rw-r--r--gcc/doc/headerdirs.texi15
2 files changed, 8 insertions, 9 deletions
diff --git a/gcc/doc/collect2.texi b/gcc/doc/collect2.texi
index a3d43b280d1..c3498c5317c 100644
--- 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 beac0ddde22..bc7f07f36be 100644
--- 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.