[patch] doc/*.texi: Fix typos and follow spelling conventions.

[Kazu Hirata <kazu at cs dot umass dot edu>]

Hi,

Attached is a patch to fix typos and follow spelling conventions.
Committed as obvious to both mainline and branch.

Kazu Hirata

2002-12-17  Kazu Hirata  <kazu@cs.umass.edu>

	* doc/c-tree.texi: Fix typos and follow spelling conventions.
	* doc/cpp.texi: Likewise.
	* doc/extend.texi: Likewise.
	* doc/gty.texi: Likewise.
	* doc/install.texi: Likewise.
	* doc/invoke.texi: Likewise.
	* doc/md.texi: Likewise.
	* doc/passes.texi: Likewise.
	* doc/rtl.texi: Likewise.
	* doc/sourcebuild.texi: Likewise.
	* doc/tm.texi: Likewise.

Index: cpp.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/cpp.texi,v
retrieving revision 1.50
diff -u -r1.50 cpp.texi
--- cpp.texi	9 Oct 2002 00:13:57 -0000	1.50
+++ cpp.texi	17 Dec 2002 16:29:30 -0000
@@ -3779,7 +3779,7 @@
 The C standard mandates this be at least 63.  CPP is limited only by
 available memory.
 
-@item Levels of parenthesised expressions within a full expression.
+@item Levels of parenthesized expressions within a full expression.
 
 The C standard requires this to be at least 63.  In preprocessor
 conditional expressions, it is limited only by available memory.
@@ -3892,9 +3892,9 @@
 same predicate.  All the answers for any given predicate are
 simultaneously true.
 
-@cindex assertions, cancelling
+@cindex assertions, canceling
 @findex #unassert
-Assertions can be cancelled with the @samp{#unassert} directive.  It
+Assertions can be canceled with the @samp{#unassert} directive.  It
 has the same syntax as @samp{#assert}.  In that form it cancels only the
 answer which was specified on the @samp{#unassert} line; other answers
 for that predicate remain true.  You can cancel an entire predicate by
Index: c-tree.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/c-tree.texi,v
retrieving revision 1.37
diff -u -r1.37 c-tree.texi
--- c-tree.texi	29 Oct 2002 22:39:49 -0000	1.37
+++ c-tree.texi	17 Dec 2002 16:29:31 -0000
@@ -64,7 +64,7 @@
 @node Deficiencies
 @section Deficiencies
 
-There are many places in which this document is incomplet and incorrekt.
+There are many places in which this document is incomplete and incorrect.
 It is, as of yet, only @emph{preliminary} documentation.
 
 @c ---------------------------------------------------------------------
Index: extend.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
retrieving revision 1.110
diff -u -r1.110 extend.texi
--- extend.texi	16 Dec 2002 18:22:22 -0000	1.110
+++ extend.texi	17 Dec 2002 16:29:36 -0000
@@ -4904,7 +4904,7 @@
 This is an implementation of the ISO C99 function @code{nan}.
 
 Since ISO C99 defines this function in terms of @code{strtod}, which we
-do not implement, a desription of the parsing is in order.  The string
+do not implement, a description of the parsing is in order.  The string
 is parsed as by @code{strtol}; that is, the base is recognized by
 leading @samp{0} or @samp{0x} prefixes.  The number parsed is placed
 in the significand such that the least significant bit of the number
@@ -6698,7 +6698,7 @@
 
 @quotation
 The storage for an object of thread storage duration shall be
-staticly initialized before the first statement of the thread startup
+statically initialized before the first statement of the thread startup
 function.  An object of thread storage duration shall not require
 dynamic initialization.
 @end quotation
Index: gty.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/gty.texi,v
retrieving revision 1.8
diff -u -r1.8 gty.texi
--- gty.texi	16 Sep 2002 18:33:21 -0000	1.8
+++ gty.texi	17 Dec 2002 16:29:36 -0000
@@ -184,10 +184,10 @@
 @findex use_params
 @item use_params
 
-When a structure contains another structure that is parameterised,
+When a structure contains another structure that is parameterized,
 there's no need to do anything special, the inner stucture inherits the
 parameters of the outer one.  When a structure contains a pointer to a
-parameterised structure, the type machinery won't automatically detect
+parameterized structure, the type machinery won't automatically detect
 this (it could, it just doesn't yet), so it's necessary to tell it that
 the pointed-to structure should use the same parameters as the outer
 structure.  This is done by marking the pointer with the
Index: install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.152
diff -u -r1.152 install.texi
--- install.texi	16 Dec 2002 18:22:23 -0000	1.152
+++ install.texi	17 Dec 2002 16:29:39 -0000
@@ -2063,7 +2063,7 @@
 The static
 library may be incorrectly built (symbols are missing at link time).
 There is a rare timing-based startup hang (probably involves an
-assupmtion about the thread library).  Multi-threaded boehm-gc (required for
+assumption about the thread library).  Multi-threaded boehm-gc (required for
 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
 4.5-RELEASE.  The alpha port may not fully bootstrap without some manual
 intervention: @command{gcjh} will crash with a floating-point exception while
Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.211
diff -u -r1.211 invoke.texi
--- invoke.texi	17 Dec 2002 14:38:59 -0000	1.211
+++ invoke.texi	17 Dec 2002 16:29:46 -0000
@@ -1608,7 +1608,7 @@
 @end smallexample
 
 @noindent
-G++ will place the @code{A} base class of @code{C} at a non-zero offset;
+G++ will place the @code{A} base class of @code{C} at a nonzero offset;
 it should be placed at offset zero.  G++ mistakenly believes that the
 @code{A} data member of @code{B} is already at offset zero.
 
@@ -2518,7 +2518,7 @@
 The idea behind this is that sometimes it is convenient (for the
 programmer) to consider floating-point values as approximations to
 infinitely precise real numbers.  If you are doing this, then you need
-to compute (by analysing the code, or in some other way) the maximum or
+to compute (by analyzing the code, or in some other way) the maximum or
 likely maximum error that the computation introduces, and allow for it
 when performing comparisons (and when producing output, but that's a
 different problem).  In particular, instead of testing for equality, you
@@ -3150,7 +3150,7 @@
 Dump after loop optimization, to @file{@var{file}.12.loop}.
 @item M
 @opindex dM
-Dump after performing the machine dependent reorganisation pass, to
+Dump after performing the machine dependent reorganization pass, to
 @file{@var{file}.33.mach}.
 @item n
 @opindex dn
Index: md.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/md.texi,v
retrieving revision 1.58
diff -u -r1.58 md.texi
--- md.texi	16 Dec 2002 18:22:24 -0000	1.58
+++ md.texi	17 Dec 2002 16:29:50 -0000
@@ -898,7 +898,7 @@
 digit should come last.
 
 This number is allowed to be more than a single digit.  If multiple
-digits are encountered consecutavely, they are interpreted as a single
+digits are encountered consecutively, they are interpreted as a single
 decimal integer.  There is scant chance for ambiguity, since to-date
 it has never been desirable that @samp{10} be interpreted as matching
 either operand 1 @emph{or} operand 0.  Should this be desired, one
@@ -965,7 +965,7 @@
 cut at the otherwise unused letters.  If it evaluates to @code{NO_REGS},
 then @code{EXTRA_CONSTRAINT} is evaluated.
 
-A typical use for @code{EXTRA_CONSTRANT} would be to distinguish certain
+A typical use for @code{EXTRA_CONSTRAINT} would be to distinguish certain
 types of memory references that affect other insn operands.
 @end ifset
 @end table
@@ -1609,7 +1609,7 @@
 @samp{c} register
 
 @item C
-Specifies constant that can be easilly constructed in SSE register without
+Specifies constant that can be easily constructed in SSE register without
 loading it from memory.
 
 @item d
@@ -5413,7 +5413,7 @@
 latency time}.  The instruction execution is not started until all
 source data have been evaluated by prior instructions (there are more
 complex cases when the instruction execution starts even when the data
-are not availaible but will be ready in given time after the
+are not available but will be ready in given time after the
 instruction execution start).  Taking the data dependence delays into
 account is simple.  The data dependence (true, output, and
 anti-dependence) delay between two instructions is given by a
Index: passes.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/passes.texi,v
retrieving revision 1.11
diff -u -r1.11 passes.texi
--- passes.texi	28 Nov 2002 20:53:02 -0000	1.11
+++ passes.texi	17 Dec 2002 16:29:51 -0000
@@ -289,7 +289,7 @@
 SSA Aggressive Dead Code Elimination.  Turned on by the @option{-fssa-dce}
 option.  This pass performs conditional constant propagation to simplify
 instructions including conditional branches.  This pass is more aggressive
-than the constant propgation done by the CSE and GCSE pases, but operates
+than the constant propagation done by the CSE and GCSE pases, but operates
 in linear time.
 
 @opindex dW
Index: rtl.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/rtl.texi,v
retrieving revision 1.44
diff -u -r1.44 rtl.texi
--- rtl.texi	15 Sep 2002 22:48:05 -0000	1.44
+++ rtl.texi	17 Dec 2002 16:29:53 -0000
@@ -2841,7 +2841,7 @@
 that do not have type @code{LABEL_NORMAL} are @dfn{alternate entry
 points} to the current function.  These may be static (visible only in
 the containing translation unit), global (exposed to all translation
-units), or weak (global, but can be overriden by another symbol with the
+units), or weak (global, but can be overridden by another symbol with the
 same name).
 
 Much of the compiler treats all four kinds of label identically.  Some
Index: sourcebuild.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/sourcebuild.texi,v
retrieving revision 1.12
diff -u -r1.12 sourcebuild.texi
--- sourcebuild.texi	13 Nov 2002 20:55:02 -0000	1.12
+++ sourcebuild.texi	17 Dec 2002 16:29:54 -0000
@@ -867,7 +867,7 @@
 FIXME: describe this.
 
 @item gcc.c-torture
-This contains particlar code fragments which have historically broken easily.
+This contains particular code fragments which have historically broken easily.
 These tests are run with multiple optimization options, so tests for features
 which only break at some optimization levels belong here.  This also contains
 tests to check that certain optimizations occur.  It might be worthwhile to 
Index: tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.183
diff -u -r1.183 tm.texi
--- tm.texi	16 Dec 2002 18:22:25 -0000	1.183
+++ tm.texi	17 Dec 2002 16:30:00 -0000
@@ -2317,7 +2317,7 @@
 @findex MODE_BASE_REG_CLASS
 @item MODE_BASE_REG_CLASS (@var{mode})
 This is a variation of the @code{BASE_REG_CLASS} macro which allows
-the selection of a base register in a mode depenedent manner.  If
+the selection of a base register in a mode dependent manner.  If
 @var{mode} is VOIDmode then it should return the same value as
 @code{BASE_REG_CLASS}.
 
@@ -4192,7 +4192,7 @@
 @findex TARGET_ASM_OUTPUT_MI_VCALL_THUNK
 @deftypefn {Target Hook} void TARGET_ASM_OUTPUT_MI_VCALL_THUNK (FILE *@var{file}, tree @var{thunk_fndecl}, HOST_WIDE_INT @var{delta}, int @var{vcall_offset}, tree @var{function})
 A function like @code{TARGET_ASM_OUTPUT_MI_THUNK}, except that if
-@var{vcall_offset} is non-zero, an additional adjustment should be made
+@var{vcall_offset} is nonzero, an additional adjustment should be made
 after adding @code{delta}.  In particular, if @var{p} is the
 adjusted pointer, the following adjustment should be made:
 
@@ -9068,7 +9068,7 @@
 @findex IFCVT_EXTRA_FIELDS
 @item IFCVT_EXTRA_FIELDS
 If defined, it should expand to a set of field declarations that will be
-added to the @code{struct ce_if_block} structure.  These should be intialized
+added to the @code{struct ce_if_block} structure.  These should be initialized
 by the @code{IFCVT_INIT_EXTRA_FIELDS} macro.
 
 @end table