summaryrefslogtreecommitdiff
path: root/gcc/df-core.c
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2007-06-13 02:27:04 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2007-06-13 02:27:04 +0000
commitbef304b8b52eab3ee756fceadade96d3410ed78e (patch)
tree53bc6532998c58f2c87be78479fff08b511afc9a /gcc/df-core.c
parented1dc2cd1ec1aafbcac80f88f3dc858c27b1d4f0 (diff)
downloadgcc-bef304b8b52eab3ee756fceadade96d3410ed78e.tar.gz
* auto-inc-dec.c, c-incpath.c, config/c4x/libgcc.S,
config/sh/divcost-analysis, dbgcnt.def, df-core.c, df-problems.c, df-scan.c, df.h, dominance.c, dse.c, regstat.c, tree-data-ref.c, tree-ssa-loop-im.c, tree-ssa-loop-prefetch.c, tree-vect-transform.c: Fix comment typos. Follow spelling conventions. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@125666 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/df-core.c')
-rw-r--r--gcc/df-core.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/gcc/df-core.c b/gcc/df-core.c
index 24c57e18392..68f6c5076e1 100644
--- a/gcc/df-core.c
+++ b/gcc/df-core.c
@@ -64,7 +64,7 @@ dataflow solution. The transfer functions are only rebuilt if the
some instruction within the block has changed.
The top layer is the dataflow solution itself. The dataflow solution
-is computed by using an efficient iterative solver and the trasfer
+is computed by using an efficient iterative solver and the transfer
functions. The dataflow solution must be recomputed whenever the
control changes or if one of the transfer function changes.
@@ -115,7 +115,7 @@ DF_ANALYZE causes all of the defined problems to be (re)solved. When
DF_ANALYZE is completes, the IN and OUT sets for each basic block
contain the computer information. The DF_*_BB_INFO macros can be used
to access these bitvectors. All deferred rescannings are down before
-the transfer functions are recompited.
+the transfer functions are recomputed.
DF_DUMP can then be called to dump the information produce to some
file. This calls DF_DUMP_START, to print the information that is not
@@ -177,7 +177,7 @@ There are four ways of doing the incremental scanning:
rescanned may be impractical. Cse and regrename fall into this
category.
-2) Defered rescanning - Calls to df_insn_rescan, df_notes_rescan, and
+2) Deferred rescanning - Calls to df_insn_rescan, df_notes_rescan, and
df_insn_delete do not immediately change the insn but instead make
a note that the insn needs to be rescanned. The next call to
df_analyze, df_finish_pass, or df_process_deferred_rescans will
@@ -635,7 +635,7 @@ df_remove_problem (struct dataflow *dflow)
/* Remove all of the problems that are not permanent. Scanning, lr,
- ur and live are permanent, the rest are removeable. Also clear all
+ ur and live are permanent, the rest are removable. Also clear all
of the changeable_flags. */
void
@@ -1505,7 +1505,7 @@ df_bb_delete (int bb_index)
dataflow infomation is not being updated properly. You can just
sprinkle calls in until you find the place that is changing an
underlying structure without calling the proper updating
- rountine. */
+ routine. */
void
df_verify (void)