mirror of
https://github.com/RPCS3/llvm.git
synced 2025-02-04 01:26:41 +00: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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@59759 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
66c75aaa02
commit
47d1a214a7
@ -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…
x
Reference in New Issue
Block a user