From 6356f8928853bc14e841e5b4e990ce2508c38f26 Mon Sep 17 00:00:00 2001 From: Kazu Hirata Date: Thu, 12 Jun 2003 19:01:08 +0000 Subject: 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 --- gcc/df.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gcc/df.c') diff --git a/gcc/df.c b/gcc/df.c index b23c286..25396bd 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) -- cgit v1.1