On Fri, 15 May 2015, Gutierrez, Anthony wrote:
Nilay,
Sorry I didn't review this before it went out, but would you mind
reverting this patch? I do believe that issueLat should remain Cycles be
allowed to be set to any value. One can certainly imagine a FU where you
have a latency of X, and yet a throughput of 1 op / Y cycles, where Y !=
X or 1.
Perhaps a patch that instead adds a comment to explain the semantics of
issueLat - as opposed to removing it - would suffice?
As of now the out-of-order cpu does not support such FUs. So such a
setting is not of any use and only causes confusion.
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
