summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/ScheduleDAG.cpp
diff options
context:
space:
mode:
authorAndrew Trick <atrick@apple.com>2013-03-01 00:19:09 +0000
committerAndrew Trick <atrick@apple.com>2013-03-01 00:19:09 +0000
commit2a8edef70b17f2736cbf4bf6f4cd676d1739b0e8 (patch)
treee04a864859b4823d2cbc53541f749ce9d6ac34fb /llvm/lib/CodeGen/ScheduleDAG.cpp
parenteb33ced08f97b42f2fcd685abc0faf6608a3649b (diff)
downloadbcm5719-llvm-2a8edef70b17f2736cbf4bf6f4cd676d1739b0e8.tar.gz
bcm5719-llvm-2a8edef70b17f2736cbf4bf6f4cd676d1739b0e8.zip
Instructions schedulers should report correct height/depth.
We avoided computing DAG height/depth during Node printing because it shouldn't depend on an otherwise valid DAG. But this has become far too annoying for the common case of a valid DAG where we want to see valid values. If doing the computation on-the-fly turns out to be a problem in practice, then I'll add a mode to the diagnostics to only force it when we're likely to have a valid DAG, otherwise explicitly print INVALID instead of bogus numbers. For now, just go for it all the time. llvm-svn: 176314
Diffstat (limited to 'llvm/lib/CodeGen/ScheduleDAG.cpp')
-rw-r--r--llvm/lib/CodeGen/ScheduleDAG.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/lib/CodeGen/ScheduleDAG.cpp b/llvm/lib/CodeGen/ScheduleDAG.cpp
index 45b4f68570b..0c40e2bf53d 100644
--- a/llvm/lib/CodeGen/ScheduleDAG.cpp
+++ b/llvm/lib/CodeGen/ScheduleDAG.cpp
@@ -329,8 +329,8 @@ void SUnit::dumpAll(const ScheduleDAG *G) const {
dbgs() << " # weak succs left : " << WeakSuccsLeft << "\n";
dbgs() << " # rdefs left : " << NumRegDefsLeft << "\n";
dbgs() << " Latency : " << Latency << "\n";
- dbgs() << " Depth : " << Depth << "\n";
- dbgs() << " Height : " << Height << "\n";
+ dbgs() << " Depth : " << getDepth() << "\n";
+ dbgs() << " Height : " << getHeight() << "\n";
if (Preds.size() != 0) {
dbgs() << " Predecessors:\n";
OpenPOWER on IntegriCloud