diff options
| author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2002-12-19 05:18:13 +0000 |
|---|---|---|
| committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2002-12-19 05:18:13 +0000 |
| commit | a8b249217e94ac0b4e83638282f5d3461d7292bd (patch) | |
| tree | a88cdafc197ec6d583f826dadc58fdeaa0a67c10 /gcc/df.c | |
| parent | db886c6470c236ea133ab824d7d654e9763aa2d9 (diff) | |
| download | gcc-a8b249217e94ac0b4e83638282f5d3461d7292bd.tar.gz | |
* ChangeLog: Follow spelling conventions.
* ChangeLog.2: Likewise.
* ChangeLog.4: Likewise.
* ChangeLog.5: Likewise.
* cppexp.c: Likewise.
* df.c: Likewise.
* gcov.c: Likewise.
* gengtype.c: Likewise.
* reload1.c: Likewise.
* sched-rgn.c: Likewise.
* stmt.c: Likewise.
* stor-layout.c: Likewise.
* timevar.c: Likewise.
* toplev.c: Likewise.
* tree.h: Likewise.
* varasm.c: Likewise.
* config/fr30/fr30.md: Likewise.
* config/i386/i386.c: Likewise.
* config/ia64/ia64.c: Likewise.
* config/pa/pa.c: Likewise.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@60281 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/df.c')
| -rw-r--r-- | gcc/df.c | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -148,10 +148,10 @@ Similarly, should the first entry in the use list be the last use 5) Working with a sub-CFG. -Often the whole CFG does not need to be analysed, for example, +Often the whole CFG does not need to be analyzed, for example, when optimising a loop, only certain registers are of interest. Perhaps there should be a bitmap argument to df_analyse to specify - which registers should be analysed? */ + which registers should be analyzed? */ #include "config.h" #include "system.h" @@ -2317,7 +2317,7 @@ df_modified_p (df, blocks) } -/* Analyse dataflow info for the basic blocks specified by the bitmap +/* Analyze dataflow info for the basic blocks specified by the bitmap BLOCKS, or for the whole CFG if BLOCKS is zero, or just for the modified blocks if BLOCKS is -1. */ int |