@cmuratori But as soon as you're tracking work at the port level, the actual throughput is 1. (Each port can do *one* of these per clock.)
@rygorous But that was only two instructions? That is not going to account for 50% of the total throughput cycles.
-
-
@rygorous I feel like it is mostly just multiple issue, like I was saying, right - the adds and muls, for example can overlap. -
@cmuratori The problem is that your throughput calc assumes that some types of superscalar issue always happen and some never happen. - Show replies
New conversation -
-
-
@cmuratori I didn't say that it was, just that you're miscounting anyway. (The rest is, as said, that you're counting throughput wrong.)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.