This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] doc/*.texi: Fix typos.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 30 May 2003 15:53:31 -0400 (EDT)
- Subject: [patch] doc/*.texi: Fix typos.
Hi,
Attached is a patch to fix typos. Committed as obvious.
Kazu Hirata
2003-05-30 Kazu Hirata <kazu@cs.umass.edu>
* doc/invoke.texi: Fix typos.
* doc/rtl.texi: Likewise.
Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.283
diff -u -r1.283 invoke.texi
--- invoke.texi 21 May 2003 21:23:03 -0000 1.283
+++ invoke.texi 30 May 2003 19:45:48 -0000
@@ -4632,10 +4632,10 @@
@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
Index: rtl.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/rtl.texi,v
retrieving revision 1.56
diff -u -r1.56 rtl.texi
--- rtl.texi 12 May 2003 13:26:02 -0000 1.56
+++ rtl.texi 30 May 2003 19:45:50 -0000
@@ -746,7 +746,7 @@
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.