inorder: don't overuse getLatency()
authorKorey Sewell <ksewell@umich.edu>
Fri, 18 Feb 2011 19:29:40 +0000 (14:29 -0500)
committerKorey Sewell <ksewell@umich.edu>
Fri, 18 Feb 2011 19:29:40 +0000 (14:29 -0500)
commita278df0b95daacb788b8442c7331f7a7f7c8aab6
treef3ca9bfcac33fd425f89035120a2cdca4adc1261
parent37df92595328d7d1443c1670cd72d4eae3b78bf7
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
src/cpu/inorder/resource.cc