From 6fc0bb99a7d0fcedd1b345da14d4dd16926b5458 Mon Sep 17 00:00:00 2001 From: Kazu Hirata Date: Sun, 28 May 2006 17:46:46 +0000 Subject: cfgcleanup.c, [...]: Fix comment typos. * 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. From-SVN: r114168 --- gcc/df-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gcc/df-core.c') 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 -- cgit v1.2.1