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

	* doc/invoke.texi, doc/options.texi, doc/plugins.texi,
	doc/tm.texi: Fix typos.

From-SVN: r155281

5 files changed, 13 insertions, 8 deletions

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 9cecb29..cfc2a43 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2009-12-16  Kazu Hirata  <kazu@codesourcery.com>
+
+	* doc/invoke.texi, doc/options.texi, doc/plugins.texi,
+	doc/tm.texi: Fix typos.
+
 2009-12-15  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
 	* doc/extend.texi (Function Attributes, Extended Asm):
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 5cfd378..e1bb207 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -15533,11 +15533,11 @@ held in @code{r13} are now pushed onto the stack.
 
 Note, common variables (variables which have not been initialised) and
 constants are not placed into the small data area as they are assigned
-to other sections in the output executeable.
+to other sections in the output executable.
 
 The default value is zero, which disables this feature.  Note, this
 feature is not enabled by default with higher optimization levels
-(@option{-O2} etc) because of the potentially deterimental effects of
+(@option{-O2} etc) because of the potentially detrimental effects of
 reserving register @code{r13}.  It is up to the programmer to
 experiment and discover whether this feature is of benefit to their
 program.
@@ -15562,7 +15562,7 @@ default option.
 @opindex mmax-constant-size
 Specifies the maxium size, in bytes, of a constant that can be used as
 an operand in a RX instruction.  Although the RX instruction set does
-allow consants of up to 4 bytes in length to be used in instructions,
+allow constants of up to 4 bytes in length to be used in instructions,
 a longer value equates to a longer instruction.  Thus in some
 circumstances it can be beneficial to restrict the size of constants
 that are used in instructions.  Constants that are too big are instead
@@ -16812,7 +16812,7 @@ that MinGW-specific thread support is to be used.
 @opindex municode
 This option is available for mingw-w64 targets.  It specifies
 that the UNICODE macro is getting pre-defined and that the
-unicode capable runtime startup code is choosen.
+unicode capable runtime startup code is chosen.
 
 @item -mwin32
 @opindex mwin32
diff --git a/gcc/doc/options.texi b/gcc/doc/options.texi
index 2041de9..284ea49 100644
--- a/gcc/doc/options.texi
+++ b/gcc/doc/options.texi
@@ -85,7 +85,7 @@ configurations and yet the masks always need to be defined.
 @section Option properties
 
 The second field of an option record can specify any of the following
-properties.  When an option takes an argument, it is enlosed in parentheses
+properties.  When an option takes an argument, it is enclosed in parentheses
 following the option property name.  The parser that handles option files
 is quite simplistic, and will be tricked by any nested parentheses within
 the argument text itself; in this case, the entire option argument can
diff --git a/gcc/doc/plugins.texi b/gcc/doc/plugins.texi
index 5562534..d446f9f 100644
--- a/gcc/doc/plugins.texi
+++ b/gcc/doc/plugins.texi
@@ -399,7 +399,7 @@ When a pass is first added to one of the pass lists, the event
 @section Building GCC plugins
 
 If plugins are enabled, GCC installs the headers needed to build a
-plugin (somehwere in the installation tree, e.g. under
+plugin (somewhere in the installation tree, e.g. under
 @file{/usr/local}).  In particular a @file{plugin/include} directory
 is installed, containing all the header files needed to build plugins.
 
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index 6a29917..5616b48 100644
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -9933,7 +9933,7 @@ contained within the @var{superset} named address space.  Pointers to
 a named address space that is a subset of another named address space
 will be converted automatically without a cast if used together in
 arithmetic operations.  Pointers to a superset address space can be
-converted to pointers to a subset address space via explict casts.
+converted to pointers to a subset address space via explicit casts.
 @end deftypefn
 
 @deftypefn {Target Hook} {rtx} TARGET_ADDR_SPACE_CONVERT (rtx @var{op}, tree @var{from_type}, tree @var{to_type})
@@ -11038,7 +11038,7 @@ On some architectures it can take multiple instructions to synthesize
 a constant.  If there is another constant already in a register that
 is close enough in value then it is preferable that the new constant
 is computed from this register using immediate addition or
-substraction.  We accomplish this through CSE.  Besides the value of
+subtraction.  We accomplish this through CSE.  Besides the value of
 the constant we also add a lower and an upper constant anchor to the
 available expressions.  These are then queried when encountering new
 constants.  The anchors are computed by rounding the constant up and