diff options
| author | Kazu Hirata <kazu@cs.umass.edu> | 2003-05-30 19:50:02 +0000 |
|---|---|---|
| committer | Kazu Hirata <kazu@gcc.gnu.org> | 2003-05-30 19:50:02 +0000 |
| commit | 65d2d7642efba08fbd9aa2c46f17ef3fedd1946a (patch) | |
| tree | 0ed9b8077839990708bba7bda78d0e8e1cb41639 /gcc/doc | |
| parent | 5c29d24c6293d8a79973c6b9af181a18961181be (diff) | |
| download | gcc-65d2d7642efba08fbd9aa2c46f17ef3fedd1946a.zip gcc-65d2d7642efba08fbd9aa2c46f17ef3fedd1946a.tar.gz gcc-65d2d7642efba08fbd9aa2c46f17ef3fedd1946a.tar.bz2 | |
invoke.texi: Fix typos.
* doc/invoke.texi: Fix typos.
* doc/rtl.texi: Likewise.
From-SVN: r67251
Diffstat (limited to 'gcc/doc')
| -rw-r--r-- | gcc/doc/invoke.texi | 4 | ||||
| -rw-r--r-- | gcc/doc/rtl.texi | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index aa7e5dc..df43850 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 58d181f..0ad9150 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. |