summaryrefslogtreecommitdiff
path: root/gcc/df.c
diff options
context:
space:
mode:
authorKazu Hirata <kazu@gcc.gnu.org>2003-06-12 19:01:08 +0000
committerKazu Hirata <kazu@gcc.gnu.org>2003-06-12 19:01:08 +0000
commit6356f8928853bc14e841e5b4e990ce2508c38f26 (patch)
tree0f2925fe84100a624006d902c347d9fea822e422 /gcc/df.c
parent25f47a4c2358896aa2498b357a51166c0024d761 (diff)
downloadgcc-6356f8928853bc14e841e5b4e990ce2508c38f26.tar.gz
ChangeLog: Follow spelling conventions.
* ChangeLog: Follow spelling conventions. * ChangeLog.2: Likewise. * c-decl.c: Likewise. * cfgloop.h: Likewise. * cgraph.c: Likewise. * coverage.c: Likewise. * cppcharset.c: Likewise. * cpphash.h: Likewise. * cpplex.c: Likewise. * cpplib.c: Likewise. * dbxout.c: Likewise. * df.c: Likewise. * dwarf2out.c: Likewise. * dwarfout.c: Likewise. * emit-rtl.c: Likewise. * explow.c: Likewise. * gcov-io.c: Likewise. * gcov-io.h: Likewise. * gcov.c: Likewise. * gengtype.c: Likewise. * ggc.h: Likewise. * opts.c: Likewise. * real.c: Likewise. * reload.c: Likewise. * stmt.c: Likewise. From-SVN: r67849
Diffstat (limited to 'gcc/df.c')
-rw-r--r--gcc/df.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/df.c b/gcc/df.c
index b23c2862b17..25396bd371a 100644
--- a/gcc/df.c
+++ b/gcc/df.c
@@ -149,7 +149,7 @@ Similarly, should the first entry in the use list be the last use
4) Working with a sub-CFG.
Often the whole CFG does not need to be analyzed, for example,
-when optimising a loop, only certain registers are of interest.
+when optimizing a loop, only certain registers are of interest.
Perhaps there should be a bitmap argument to df_analyse to specify
which registers should be analyzed?
@@ -885,7 +885,7 @@ df_ref_record (df, reg, loc, insn, ref_type, ref_flags)
}
-/* Return non-zero if writes to paradoxical SUBREGs, or SUBREGs which
+/* Return nonzero if writes to paradoxical SUBREGs, or SUBREGs which
are too narrow, are read-modify-write. */
bool
read_modify_subreg_p (x)