summaryrefslogtreecommitdiff
path: root/gcc/df-core.c
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2006-05-28 17:46:46 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2006-05-28 17:46:46 +0000
commit554f270788f1a960804f94da4b28faed8fcf50b2 (patch)
treebfad2d717d3d9605e8fb4c3cba410dc93fdf4df4 /gcc/df-core.c
parentbf3d6235698dd6eeffcea4a95724f4bd37d95861 (diff)
downloadgcc-554f270788f1a960804f94da4b28faed8fcf50b2.tar.gz
* cfgcleanup.c, cfgexpand.c, cgraphunit.c, config/arm/arm.c,
config/fr30/fr30.md, config/i386/i386-interix.h, config/i386/i386.c, config/i386/i386.md, config/sh/superh.h, config/sh/superh64.h, config/v850/v850.c, df-core.c, df-problems.c, df.h, except.c, final.c, haifa-sched.c, lambda-code.c, libgcc2.h, omp-low.c, optabs.c, predict.c, reload.c, tree-flow.h, tree-outof-ssa.c, tree-ssa-dce.c, tree-ssa-pre.c, tree-vect-transform.c: Fix comment typos. Follow spelling conventions. * doc/invoke.texi, doc/rtl.texi, doc/tm.texi: Fix typos. Follow spelling conventions. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@114168 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/df-core.c')
-rw-r--r--gcc/df-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/df-core.c b/gcc/df-core.c
index f0c62c91c1e..7f89fccdfb3 100644
--- a/gcc/df-core.c
+++ b/gcc/df-core.c
@@ -164,7 +164,7 @@ incremental algorithms.
As for the bit vector problems, there is no interface to give a set of
blocks over with to resolve the iteration. In general, restarting a
dataflow iteration is difficult and expensive. Again, the best way to
-keep the dataflow infomation up to data (if this is really what is
+keep the dataflow information up to data (if this is really what is
needed) it to formulate a problem specific solution.
There are fine grained calls for creating and deleting references from