diff options
| author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2002-09-27 12:48:07 +0000 |
|---|---|---|
| committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2002-09-27 12:48:07 +0000 |
| commit | f712a0dcd3010d64361b11d5f7b7d71700f69aab (patch) | |
| tree | c2f7682329bf354ca96d9ae19d6a6cfe4312c16a /gcc/sched-rgn.c | |
| parent | 5d822c0058e6e4da7d30bd003fd9696370a88aef (diff) | |
| download | gcc-f712a0dcd3010d64361b11d5f7b7d71700f69aab.tar.gz | |
* LANGUAGES: Follow spelling conventions.
* rtl.def: Likewise.
* sbitmap.c: Likewise.
* sched-int.h: Likewise.
* sched-rgn.c: Likewise.
* sibcall.c: Likewise.
* simplify-rtx.c: Likewise.
* ssa.c: Likewise.
* stab.def: Likewise.
* stmt.c: Likewise.
* stor-layout.c: Likewise.
* target.h: Likewise.
* timevar.c: Likewise.
* toplev.c: Likewise.
* tree-dump.c: Likewise.
* tree-inline.c: Likewise.
* tree.c: Likewise.
* tree.def: Likewise.
* tree.h: Likewise.
* unroll.c: Likewise.
* varasm.c: Likewise.
* vmsdbgout.c: Likewise.
* treelang/treelang.texi: Likewise.
* treelang/treetree.c: Likewise.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@57587 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/sched-rgn.c')
| -rw-r--r-- | gcc/sched-rgn.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/sched-rgn.c b/gcc/sched-rgn.c index f9b762ee932..6853a2e6a0a 100644 --- a/gcc/sched-rgn.c +++ b/gcc/sched-rgn.c @@ -3001,7 +3001,7 @@ schedule_insns (dump_file) first so that we can verify that live_at_start didn't change. Then do all other blocks. */ /* ??? There is an outside possibility that update_life_info, or more - to the point propagate_block, could get called with non-zero flags + to the point propagate_block, could get called with nonzero flags more than once for one basic block. This would be kinda bad if it were to happen, since REG_INFO would be accumulated twice for the block, and we'd have twice the REG_DEAD notes. |