sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

inorder: don't overuse getLatency()

Browse source 
resources don't need to call getLatency because the latency is already a member
in the class. If there is some type of special case where different instructions
impose a different latency inside a resource then we can revisit this and
add getLatency() back in
This commit is contained in:
Korey Sewell 2011-02-18 14:29:40 -05:00
parent 37df925953
commit a278df0b95
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/cpu/inorder/resource.cc
View file

@ -325,10 +325,8 @@ Resource::ticks(int num_cycles)
void
Resource::scheduleExecution(int slot_num)
{
int res_latency = getLatency(slot_num);
if (res_latency >= 1) {
scheduleEvent(slot_num, res_latency);
if (latency >= 1) {
scheduleEvent(slot_num, latency);
} else {
execute(slot_num);
}