summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2003-05-30 19:50:02 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2003-05-30 19:50:02 +0000
commitb3e17f149db1db4efb165dbdd46daaed2c35ade6 (patch)
tree0ed9b8077839990708bba7bda78d0e8e1cb41639
parent4209f9b275b39f6fe5550ed54f25ba3c249fd70c (diff)
downloadgcc-b3e17f149db1db4efb165dbdd46daaed2c35ade6.tar.gz
* doc/invoke.texi: Fix typos.
* doc/rtl.texi: Likewise. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@67251 138bc75d-0d04-0410-961f-82ee72b054a4
-rw-r--r--gcc/ChangeLog5
-rw-r--r--gcc/doc/invoke.texi4
-rw-r--r--gcc/doc/rtl.texi2
3 files changed, 8 insertions, 3 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 36afa305490..d98af3a1d34 100644
--- 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 aa7e5dc4d6f..df4385049c1 100644
--- 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 58d181fa569..0ad91508b34 100644
--- 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.