extend.texi, [...]: Fix typos.

	* doc/extend.texi, doc/invoke.texi, doc/passes.texi: Fix
	typos.  Follow spelling conventions.

From-SVN: r87293

5 files changed, 13 insertions, 8 deletions

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 2e6dcd0..d3b8fc0 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2004-09-10  Kazu Hirata  <kazu@cs.umass.edu>
+
+	* doc/extend.texi, doc/invoke.texi, doc/passes.texi: Fix
+	typos.  Follow spelling conventions.
+
 2004-09-10  Joseph S. Myers  <jsm@polyomino.org.uk>
 
 	* toplev.c (warn_deprecated_use): Correct logic for saying "type"
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 63cefd3..ccab95a 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -5538,7 +5538,7 @@ Semiconductor}.  The two exceptions are @code{__MDUNPACKH} and
 pointer rather than by value.
 
 Most of the functions are named after specific FR-V instructions.
-Such functions are said to be ``directly mapped'' and are summarised
+Such functions are said to be ``directly mapped'' and are summarized
 here in tabular form.
 
 @menu
@@ -8904,7 +8904,7 @@ translation unit.
 @emph{Note:} As of GCC 2.7.2, these @code{#pragma}s are not useful in
 most cases, because of COMDAT support and the ``key method'' heuristic
 mentioned in @ref{Vague Linkage}.  Using them can actually cause your
-program to grow due to unnecesary out-of-line copies of inline
+program to grow due to unnecessary out-of-line copies of inline
 functions.  Currently (3.4) the only benefit of these
 @code{#pragma}s is reduced duplication of debugging information, and
 that should be addressed soon on DWARF 2 targets with the use of
diff --git a/gcc/doc/include/texinfo.tex b/gcc/doc/include/texinfo.tex
index 9500f18..49747b0 100644
--- a/gcc/doc/include/texinfo.tex
+++ b/gcc/doc/include/texinfo.tex
@@ -403,7 +403,7 @@
 \def\argremovecomment#1\comment#2\ArgTerm{\argremovec #1\c\ArgTerm}
 \def\argremovec#1\c#2\ArgTerm{\argcheckspaces#1\^^M\ArgTerm}
 
-% Each occurence of `\^^M' or `<space>\^^M' is replaced by a single space.
+% Each occurrence of `\^^M' or `<space>\^^M' is replaced by a single space.
 %
 % \argremovec might leave us with trailing space, e.g.,
 %    @end itemize  @c foo
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 6bf49e4..94b4757 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -5527,7 +5527,7 @@ variable will then be made to alias every call-clobbered variable.
 
 @item max-aliased-vops
 
-Maxiumum number of virtual operands allowed to represent aliases
+Maximum number of virtual operands allowed to represent aliases
 before triggering the alias grouping heuristic.  Alias grouping
 reduces compile times and memory consumption needed for aliasing at
 the expense of precision loss in alias information.
@@ -12109,9 +12109,9 @@ The default without @option{-fpic} is @code{initial-exec}; with
 @item -fvisibility=@var{default|internal|hidden|protected}
 @opindex fvisibility
 Set the default ELF image symbol visibility to the specified option - all
-symbols will be marked with this unless overrided within the code.
+symbols will be marked with this unless overridden within the code.
 Using this feature can very substantially improve linking and
-load times of shared object libraries, produce more optimised
+load times of shared object libraries, produce more optimized
 code, provide near-perfect API export and prevent symbol clashes.
 It is @strong{strongly} recommended that you use this in any shared objects
 you distribute.
diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
index 0ffeae7..f7f3873 100644
--- a/gcc/doc/passes.texi
+++ b/gcc/doc/passes.texi
@@ -79,7 +79,7 @@ usually most convenient to do this as each top level declaration or
 definition is seen.  There is also a distinction to be made between
 generating functional code and generating complete debug information.
 The only thing that is absolutely required for functional code is that
-function and data @emph{defintions} be passed to the middle-end.  For
+function and data @emph{definitions} be passed to the middle-end.  For
 complete debug information, function, data and type declarations 
 should all be passed as well.
 
@@ -244,7 +244,7 @@ and is described by @code{pass_referenced_vars}.
 
 This pass rewrites the function such that it is in SSA form.  After
 this pass, all @code{is_gimple_reg} variables will be referenced by
-@code{SSA_NAME}, and all occurences of other variables will be 
+@code{SSA_NAME}, and all occurrences of other variables will be 
 annotated with @code{VDEFS} and @code{VUSES}; phi nodes will have 
 been inserted as necessary for each basic block.  This pass is
 located in @file{tree-ssa.c} and is described by @code{pass_build_ssa}.