mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-24 11:42:57 +01:00
Change these schedulers to not emit no-ops. It turns out that
the RR scheduler actually does look at latency values, but it doesn't use a hazard recognizer so it has no way to know when a no-op is needed, as opposed to just stalling and incrementing the cycle count. llvm-svn: 59759
This commit is contained in:
parent
4020b2b907
commit
66e692dd8f
@ -577,9 +577,7 @@ void ScheduleDAGFast::ListScheduleBottomUp() {
|
||||
}
|
||||
NotReady.clear();
|
||||
|
||||
if (!CurSU)
|
||||
Sequence.push_back(0);
|
||||
else
|
||||
if (CurSU)
|
||||
ScheduleNodeBottomUp(CurSU, CurCycle);
|
||||
++CurCycle;
|
||||
}
|
||||
|
@ -1052,9 +1052,7 @@ void ScheduleDAGRRList::ListScheduleBottomUp() {
|
||||
}
|
||||
NotReady.clear();
|
||||
|
||||
if (!CurSU)
|
||||
Sequence.push_back(0);
|
||||
else
|
||||
if (CurSU)
|
||||
ScheduleNodeBottomUp(CurSU, CurCycle);
|
||||
++CurCycle;
|
||||
}
|
||||
@ -1152,9 +1150,7 @@ void ScheduleDAGRRList::ListScheduleTopDown() {
|
||||
AvailableQueue->push_all(NotReady);
|
||||
NotReady.clear();
|
||||
|
||||
if (!CurSU)
|
||||
Sequence.push_back(0);
|
||||
else
|
||||
if (CurSU)
|
||||
ScheduleNodeTopDown(CurSU, CurCycle);
|
||||
++CurCycle;
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user