c-tree.texi: Fix typos.

2000-11-08  Jan van Male  <jan.vanmale@fenk.wau.nl>

        * c-tree.texi: Fix typos.
        * extend.texi: Likewise
        * gcov.texi: Likewise
        * rtl.texi: Likewise
        * tm.texi: Likewise

From-SVN: r37362

gcc/ChangeLog

+2000-11-09  Jan van Male  <jan.vanmale@fenk.wau.nl>
+
+        * c-tree.texi: Fix typos.
+        * extend.texi: Likewise
+        * gcov.texi: Likewise
+        * rtl.texi: Likewise
+        * tm.texi: Likewise
+
 2000-11-09  Hans-Peter Nilsson  <hp@axis.com>
 
 	* c-lex.c [! NO_IMPLICIT_EXTERN_C] (cb_enter_file): Check

gcc/c-tree.texi

@@ -578,7 +578,7 @@ more information, see @pxref{Classes}.
 
 @item UNKNOWN_TYPE
 This node is used to represent a type the knowledge of which is
-unsufficiant for a sound processing.
+insufficient for a sound processing.
 
 @item OFFSET_TYPE
 This node is used to represent a data member; for example a
@@ -1066,7 +1066,7 @@ An @code{OVERLOAD} node is not a declaration, so none of the
 @code{OVERLOAD} node in the list of overloaded functions.  The macros
 @code{OVL_CURRENT} and @code{OVL_NEXT} are actually polymorphic; you can
 use them to work with @code{FUNCTION_DECL} nodes as well as with
-overlods.  In the case of a @code{FUNCTION_DECL}, @code{OVL_CURRENT}
+overloads.  In the case of a @code{FUNCTION_DECL}, @code{OVL_CURRENT}
 will always return the function itself, and @code{OVL_NEXT} will always
 be @code{NULL_TREE}.
 
@@ -1087,13 +1087,13 @@ the @code{DECL_REAL_CONTEXT} for @code{f} will be the
 @code{RECORD_TYPE} for @code{C}.
 
 The @code{DECL_REAL_CONTEXT} and @code{DECL_CLASS_CONTEXT} are not
-availble in C; instead you should simply use @code{DECL_CONTEXT}.  In C,
+available in C; instead you should simply use @code{DECL_CONTEXT}.  In C,
 the @code{DECL_CONTEXT} for a function maybe another function.  This
 representation indicates that the GNU nested function extension is in
 use.  For details on the semantics of nested functions, see the GCC
 Manual.  The nested function can refer to local variables in its
 containing function.  Such references are not explicitly marked in the
-tree sturcture; back-ends must look at the @code{DECL_CONTEXT} for the
+tree structure; back-ends must look at the @code{DECL_CONTEXT} for the
 referenced @code{VAR_DECL}.  If the @code{DECL_CONTEXT} for the
 referenced @code{VAR_DECL} is not the same as the function currently
 being processed, and neither @code{DECL_EXTERNAL} nor @code{DECL_STATIC}
@@ -1125,7 +1125,7 @@ function, and the back-end must take appropriate action.
 @findex DECL_DESTRUCTOR_P
 @findex DECL_OVERLOADED_OPERATOR_P
 @findex DECL_CONV_FN_P
-@findex DECL_ARTIFIICIAL
+@findex DECL_ARTIFICIAL
 @findex DECL_GLOBAL_CTOR_P
 @findex DECL_GLOBAL_DTOR_P
 @findex GLOBAL_INIT_PRIORITY
@@ -1222,7 +1222,7 @@ This macro holds if the function is a destructor.
 
 @item DECL_COMPLETE_DESTRUCTOR_P
 This predicate holds if the function is the destructor for an object a
-complet type.
+complete type.
 
 @item DECL_OVERLOADED_OPERATOR_P
 This macro holds if the function is an overloaded operator.
@@ -1652,7 +1652,7 @@ as if the @code{SCOPE_STMT} were not present at all.
 These statements represent the location to which control is transferred
 when an exception is thrown.  The @code{START_CATCH_TYPE} is the type of
 exception that will be caught by this handler; it is equal (by pointer
-equalit) to @code{CATCH_ALL_TYPE} if this handler is for all types.
+equality) to @code{CATCH_ALL_TYPE} if this handler is for all types.
 
 @item SUBOBJECT
 
@@ -2120,7 +2120,7 @@ always be present in the internal representation.
 @item CALL_EXPR
 These nodes are used to represent calls to functions, including
 non-static member functions.  The first operand is a pointer to the
-function to call; it is always an expresion whose type is a
+function to call; it is always an expression whose type is a
 @code{POINTER_TYPE}.  The second argument is a @code{TREE_LIST}.  The
 arguments to the call appear left-to-right in the list.  The
 @code{TREE_VALUE} of each list node contains the expression
@@ -2176,7 +2176,7 @@ non-zero, then the loop should be exited.  An @code{EXIT_EXPR} will only
 appear within a @code{LOOP_EXPR}.
 
 @item CLEANUP_POINT_EXPR
-These nodes represent full-expressions.  The single oeprand is an
+These nodes represent full-expressions.  The single operand is an
 expression to evaluate.  Any destructor calls engendered by the creation
 of temporaries during the evaluation of that expression should be
 performed immediately after the expression is evaluated.
@@ -2209,7 +2209,7 @@ storage is initialized to zero.
 A @code{SAVE_EXPR} represents an expression (possibly involving
 side-effects) that is used more than once.  The side-effects should
 occur only the first time the expression is evaluated.  Subsequent uses
-should juse reuse the computed value.  The first operand to the
+should just reuse the computed value.  The first operand to the
 @code{SAVE_EXPR} is the expression to evaluate.  The side-effects should
 be executed where the @code{SAVE_EXPR} is first encountered in a
 depth-first preorder traversal of the expression tree.

gcc/extend.texi

@@ -853,7 +853,7 @@ decimal notation, such as @code{1.55e1}, but also numbers such as
 @code{0x1.fp3} written in hexadecimal format.  In that format the
 @code{0x} hex introducer and the @code{p} or @code{P} exponent field are
 mandatory.  The exponent is a decimal number that indicates the power of
-2 by which the significand part will be multiplied.  Thus @code{0x1.f} is
+2 by which the significant part will be multiplied.  Thus @code{0x1.f} is
 1 15/16, @code{p3} multiplies it by 8, and the value of @code{0x1.fp3}
 is the same as @code{1.55e1}.
 
@@ -2702,7 +2702,7 @@ region.
 
 An @code{asm} instruction without any operands or clobbers (and ``old
 style'' @code{asm}) will not be deleted or moved significantly,
-regardless, unless it is unreachable, the same wasy as if you had
+regardless, unless it is unreachable, the same way as if you had
 written a @code{volatile} keyword.
 
 Note that even a volatile @code{asm} instruction can be moved in ways

gcc/gcov.texi

@@ -217,7 +217,7 @@ For a call, if it was executed at least once, then a percentage
 indicating the number of times the call returned divided by the number
 of times the call was executed will be printed.  This will usually be
 100%, but may be less for functions call @code{exit} or @code{longjmp},
-and thus may not return everytime they are called.
+and thus may not return every time they are called.
 
 The execution counts are cumulative.  If the example program were
 executed again without removing the @code{.da} file, the count for the
@@ -336,7 +336,7 @@ The format of the @code{.da} file is fairly simple.  The first 8-byte
 number is the number of counts in the file, followed by the counts
 (stored as 8-byte numbers).  Each count corresponds to the number of
 times each arc in the program is executed.  The counts are cumulative;
-each time the program is executed, it attemps to combine the existing
+each time the program is executed, it attempts to combine the existing
 @code{.da} files with the new counts for this invocation of the
 program.  It ignores the contents of any @code{.da} files whose number of
 arcs doesn't correspond to the current program, and merely overwrites

gcc/rtl.texi

@@ -2210,7 +2210,7 @@ expressions and so is @var{base}.  The mode @var{m} specifies how much
 space is given to each address-difference.  @var{min} and @var{max}
 are set up by branch shortening and hold a label with a minimum and a
 maximum address, respectively.  @var{flags} indicates the relative
-position of @var{base}, @var{min} and @var{max} to the cointaining insn
+position of @var{base}, @var{min} and @var{max} to the containing insn
 and of @var{min} and @var{max} to @var{base}.  See rtl.def for details.@refill
 @end table
 
@@ -2915,7 +2915,7 @@ probability that the branch will be taken.
 @findex REG_BR_PRED
 @item REG_BR_PRED
 These notes are found in JUMP insns after delayed branch scheduling
-has taken place.  They indicate both the direction and the likelyhood
+has taken place.  They indicate both the direction and the likelihood
 of the JUMP.  The format is a bitmask of ATTR_FLAG_* values.
 
 @findex REG_FRAME_RELATED_EXPR

gcc/tm.texi

@@ -6017,7 +6017,7 @@ correct for most systems.
 @findex ASM_OUTPUT_DEF_FROM_DECLS
 @item ASM_OUTPUT_DEF_FROM_DECLS (@var{stream}, @var{decl_of_name}, @var{decl_of_value})
 A C statement to output to the stdio stream @var{stream} assembler code
-which defines (equates) the symbol whoes tree node is @var{decl_of_name}
+which defines (equates) the symbol whose tree node is @var{decl_of_name}
 to have the value of the tree node @var{decl_of_value}.  This macro will
 be used in preference to @samp{ASM_OUTPUT_DEF} if it is defined and if
 the tree nodes are available.
@@ -6276,7 +6276,7 @@ This is like @code{ASM_OUTPUT_CONSTRUCTOR} but used for termination
 functions rather than initialization functions.
 
 When @code{ASM_OUTPUT_CONSTRUCTOR} and @code{ASM_OUTPUT_DESTRUCTOR} are
-defined, the initializaiton routine generated for the generated object
+defined, the initialization routine generated for the generated object
 file will have static linkage.
 @end table
 
@@ -6490,11 +6490,11 @@ files can define these macros differently.
 
 @item ASM_FPRINTF_EXTENSIONS(@var{file}, @var{argptr}, @var{format})
 @findex ASM_FPRINTF_EXTENSIONS
-If defiend this macro should expand to a series of @code{case}
+If defined this macro should expand to a series of @code{case}
 statements which will be parsed inside the @code{switch} statement of
 the @code{asm_fprintf} function.  This allows targets to define extra
 printf formats which may useful when generating their assembler
-statements.  Noet that upper case letters are reserved for future
+statements.  Note that upper case letters are reserved for future
 generic extensions to asm_fprintf, and so are not available to target
 specific code.  The output file is given by the parameter @var{file}.
 The varargs input pointer is @var{argptr} and the rest of the format
@@ -7865,7 +7865,7 @@ The primary reason to define this macro is to provide compatibility with
 other compilers for the same target.  In general, we discourage
 definition of target-specific pragmas for GCC.
 
-If the pragma can be implemented by atttributes then the macro
+If the pragma can be implemented by attributes then the macro
 @samp{INSERT_ATTRIBUTES} might be a useful one to define as well.
 
 Preprocessor macros that appear on pragma lines are not expanded.  All