From: Korey Sewell <ksewell@umich.edu>
Date: Fri, 18 Feb 2011 19:29:40 +0000 (-0500)
Subject: inorder: don't overuse getLatency()
X-Git-Tag: stable_2012_02_02~553^2~9
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=a278df0b95daacb788b8442c7331f7a7f7c8aab6;p=gem5.git

inorder: don't overuse getLatency()
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
---

diff --git a/src/cpu/inorder/resource.cc b/src/cpu/inorder/resource.cc
index 6a2f5e62a..701785658 100644
--- a/src/cpu/inorder/resource.cc
+++ b/src/cpu/inorder/resource.cc
@@ -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);
     }