c-tree.texi, [...]: Consistently use "front end" and "back end" as nouns and "front-end" and...

	* 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.

From-SVN: r43479

gcc/ChangeLog

+2001-06-21  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* 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.
+
 Wed Jun 20 21:53:35 CEST 2001  Jan Hubicka  <jh@suse.cz>
 
 	* predict.c (estimate_probability): Fix loop bounds.

gcc/doc/contrib.texi

@@ -28,7 +28,7 @@ the Intel 80387 register stack.
 Alasdair Baird for various bugfixes.
 
 @item
-Gerald Baumgartner added the signature extension to the C++ front-end.
+Gerald Baumgartner added the signature extension to the C++ front end.
 
 @item
 Neil Booth for various work on cpplib.
@@ -282,7 +282,7 @@ Kriang Lerdsuwanakij for improvements to demangler and various c++ fixes.
 
 @item
 Warren Levy major work on libgcj (Java Runtime Library) and random
-work on the Java front-end.
+work on the Java front end.
 
 @item
 Alain Lichnewsky ported GCC to the Mips cpu.

gcc/doc/extend.texi

@@ -2394,7 +2394,7 @@ attributes are currently defined for variables: @code{aligned},
 @code{transparent_union}, @code{unused}, and @code{weak}.  Some other
 attributes are defined for variables on particular target systems.  Other
 attributes are available for functions (@pxref{Function Attributes}) and
-for types (@pxref{Type Attributes}).  Other front-ends might define more
+for types (@pxref{Type Attributes}).  Other front ends might define more
 attributes (@pxref{C++ Extensions,,Extensions to the C++ Language}).
 
 You may also specify attributes with @samp{__} preceding and following

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

gcc/doc/install-old.texi

@@ -127,7 +127,7 @@ linker with GNU CC.
 This option does not cause the GNU linker to be installed; it just
 modifies the behavior of GNU CC to work with the GNU linker.
 @c Specifically, it inhibits the installation of @code{collect2}, a program
-@c which otherwise serves as a front-end for the system's linker on most
+@c which otherwise serves as a front end for the system's linker on most
 @c configurations.
 
 @item --with-stabs
@@ -767,7 +767,7 @@ make minor changes in @file{make-cccp.com} and @file{make-cc1.com}
 to choose alternate definitions of @code{CC}, @code{CFLAGS}, and
 @code{LIBS}.  See comments in those files.  However, you must
 also have a working version of the GNU assembler (GNU as, aka GAS) as
-it is used as the back-end for GNU CC to produce binary object modules
+it is used as the back end for GNU CC to produce binary object modules
 and is not included in the GNU CC sources.  GAS is also needed to
 compile @file{libgcc2} in order to build @file{gcclib} (see above);
 @file{make-l2.com} expects to be able to find it operational in

gcc/doc/install.texi

@@ -33,7 +33,7 @@
 @settitle Installing GCC: Binaries
 @end ifset
 
-@comment $Id: install.texi,v 1.28 2001/06/15 17:35:48 ro Exp $
+@comment $Id: install.texi,v 1.29 2001/06/15 22:25:18 ljrittle Exp $
 @c Copyright (C) 2001 Free Software Foundation, Inc.
 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
 
@@ -192,9 +192,9 @@ are also included in the full distribution.
 
 If you choose to download specific components, you must download the core
 gcc distribution plus any language specific distributions you wish to
-use.  The core distribution includes the C language front-end as well as the
+use.  The core distribution includes the C language front end as well as the
 shared components. Each language has a tarball which includes the language
-front-end as well as the language runtime (when appropriate).
+front end as well as the language runtime (when appropriate).
 
 Unpack the core distribution as well as any language specific
 distributions in the same directory.
@@ -561,7 +561,7 @@ Specify that the run-time libraries
 used by GCJ should not be built.  This is useful in case you intend
 to use GCJ with some other run-time, or you're going to install it
 separately, or it just happens not to build on your particular
-machine.  In general, if the Java front-end is enabled, the GCJ
+machine.  In general, if the Java front end is enabled, the GCJ
 libraries will be enabled too, unless they're known to not work on
 the target platform.  If GCJ is enabled but libgcj isn't built, you
 may need to port it; in this case, before modifying the top-level

gcc/doc/invoke.texi

@@ -1688,16 +1688,16 @@ Traditionally, diagnostic messages have been formatted irrespective of
 the output device's aspect (e.g. its width, @dots{}).  The options described
 below can be used to control the diagnostic messages formatting
 algorithm, e.g. how many characters per line, how often source location
-information should be reported.  Right now, only the C++ front-end can
+information should be reported.  Right now, only the C++ front end can
 honor these options.  However it is expected, in the near future, that
-the remaining front-ends would be able to digest them correctly.
+the remaining front ends would be able to digest them correctly.
 
 @table @gcctabopt
 @item -fmessage-length=@var{n}
 @opindex fmessage-length
 Try to format error messages so that they fit on lines of about @var{n}
 characters.  The default is 72 characters for g++ and 0 for the rest of
-the front-ends supported by GCC.  If @var{n} is zero, then no
+the front ends supported by GCC.  If @var{n} is zero, then no
 line-wrapping will be done; each error message will appear on a single
 line.
 

gcc/doc/rtl.texi

@@ -380,7 +380,7 @@ never be simultaneously set.
 In @code{mem} expressions, the alias set to which @var{x} belongs.  If
 zero, @var{x} is not in any alias set, and may alias anything.  If
 nonzero, @var{x} may only alias objects in the same alias set.  This
-value is set (in a language-specific manner) by the front-end.  This
+value is set (in a language-specific manner) by the front end.  This
 field is not a bit-field; it is in an integer, found as the second
 argument to the @code{mem}.