diff options
| author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-21 00:03:48 +0000 |
|---|---|---|
| committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-21 00:03:48 +0000 |
| commit | a3ff64f5acacd90a936bf8af3fb19159dcca6fd3 (patch) | |
| tree | 43efbb988a673849f67b78d80a9342d1dda12331 /gcc/doc/gcc.texi | |
| parent | 609f152b76290bb424b3049375bb38b699de8385 (diff) | |
| download | gcc-a3ff64f5acacd90a936bf8af3fb19159dcca6fd3.tar.gz | |
* doc/c-tree.texi, doc/contrib.texi, doc/extend.texi,
doc/gcc.texi, doc/install-old.texi, doc/install.texi,
doc/invoke.texi, doc/rtl.texi: Consistently use "front end" and
"back end" as nouns and "front-end" and "back-end" as adjectives.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@43479 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/gcc.texi')
| -rw-r--r-- | gcc/doc/gcc.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gcc/doc/gcc.texi b/gcc/doc/gcc.texi index e1bbb512a4c..1fe70664072 100644 --- a/gcc/doc/gcc.texi +++ b/gcc/doc/gcc.texi @@ -42,12 +42,12 @@ @c anything else? --mew 10feb93 @c For consistency, use the following: +@c - "back end" as a noun, "back-end" as an adjective. @c - "bit-field" not "bitfield" or "bit field" (following the C and C++ @c standards). @c - "built-in" as an adjective ("built-in function"), or sometimes @c "built in", not "builtin" (which isn't a word). -@c - "front end" as a noun, "front-end" as an adjective (not yet -@c consistently followed). +@c - "front end" as a noun, "front-end" as an adjective. @macro gcctabopt{body} @code{\body\} @@ -263,7 +263,7 @@ bugs. It corresponds to GCC version 3.1. * Portability:: Goals of GCC's portability features. * Interface:: Function-call interface of GCC output. * Passes:: Order of passes, what they do, and what each file is for. -* Trees:: The source representation used by the C and C++ front-ends. +* Trees:: The source representation used by the C and C++ front ends. * RTL:: The intermediate representation that most passes work on. * Machine Desc:: How to write machine description instruction patterns. * Target Macros:: How to write the machine description C macros. @@ -316,7 +316,7 @@ compiler. For example, we refer to the optimization options as affecting the behavior of ``GCC'' or sometimes just ``the compiler''. Front ends for other languages, such as Ada 95 and Pascal exist but -have not yet been integrated into GCC. These front-ends, like that for C++, +have not yet been integrated into GCC. These front ends, like that for C++, are built in subdirectories of GCC and link to it. The result is an integrated compiler that can compile programs written in C, C++, Objective C, or any of the languages for which you have installed front |