diff options
author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2007-07-28 23:55:00 +0000 |
---|---|---|
committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2007-07-28 23:55:00 +0000 |
commit | 4a7e4fcc3dc597410d1b6b6d0e245e9b1c107c9b (patch) | |
tree | def25d7a21ae681586ef447d7554b6b4d334b0d5 /gcc/df-core.c | |
parent | ce1640f14baafa9b1c9a0b808ed48ee9ae8f5643 (diff) | |
download | gcc-4a7e4fcc3dc597410d1b6b6d0e245e9b1c107c9b.tar.gz |
* cfglayout.c, config/arm/arm.c, config/arm/cortex-a8.md,
config/arm/neon-schedgen.ml, config/arm/neon.ml,
config/arm/vec-common.md, config/ia64/div.md, cselib.c,
df-core.c, df.h, dominance.c, optabs.c, opts.c, reg-stack.c,
regstat.c, target.h, tree-ssa-live.c, tree-ssa-pre.c,
tree-vect-transform.c, tree.def: Fix comment typos. Follow
spelling conventions.
* doc/invoke.texi: Follow spelling conventions.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@127030 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/df-core.c')
-rw-r--r-- | gcc/df-core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/df-core.c b/gcc/df-core.c index 16e55b752ff..453d61a999f 100644 --- a/gcc/df-core.c +++ b/gcc/df-core.c @@ -144,7 +144,7 @@ There are four ways of doing the incremental scanning: For most modern rtl passes, this is certainly the easiest way to manage rescanning the insns. This technique also has the advantage that the scanning information is always correct and can be relied - apon even after changes have been made to the instructions. This + upon even after changes have been made to the instructions. This technique is contra indicated in several cases: a) If def-use chains OR use-def chains (but not both) are built, |