invoke.texi: Fix typos.

	* doc/invoke.texi: Fix typos.
	* doc/rtl.texi: Likewise.

From-SVN: r67251

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 36afa305490501f278ef1dbcb151f68e050c6b15..d98af3a1d344f34b2eb04fe20e9f21e69b9fd6c6 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2003-05-30  Kazu Hirata  <kazu@cs.umass.edu>
+
+       * doc/invoke.texi: Fix typos.
+       * doc/rtl.texi: Likewise.
+
 2003-05-30  Dhananjay Deshpande  <dhananjayd@kpitcummins.com>
 
        * config/h8300/crti.asm: Use .h8300hn and .h8300sn for normal

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index aa7e5dc4d6f011f55028488064cc3940f8e3c228..df4385049c1a0c2e7fe6ec46722cbd076cfbc288 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -4632,10 +4632,10 @@ collection to occur at every opportunity.
 @item reorder-blocks-duplicate
 @itemx reorder-blocks-duplicate-feedback
 
-Used by basic block reordering pass to decide whether to use uncondtional
+Used by basic block reordering pass to decide whether to use unconditional
 branch or duplicate the code on it's destination.  Code is duplicated when it's
 estimated size is smaller than this value multiplied by the estimated size of
-unconditinal jump in the hot spots of the program.
+unconditional jump in the hot spots of the program.
 
 The @option{reorder-block-duplicate-feedback} is used only when profile
 feedback is available and may be set to higher values than

diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 58d181fa569a10b1ae4c290dacfcc3ab6c69b691..0ad91508b34b1d1cb69821b88a5bc8a95bbe822c 100644 (file)
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -746,7 +746,7 @@ a non-unchanging read can conflict with a non-unchanging write; an
 unchanging read can conflict with an unchanging write (since there may
 be a single store to this address to initialize it); and an unchanging
 store can conflict with a non-unchanging read.  This means we must make
-conservative assumptions when chosing the value of this flag for a
+conservative assumptions when choosing the value of this flag for a
 memory reference to an object containing both unchanging and
 non-unchanging fields: we must set the flag when writing to the object
 and clear it when reading from the object.