On Feb 17, 2009, at 11:18 PM, Steve Reinhardt wrote: > > The idea of the merge() step (mapping *all* registers to a single > integer namespace) was actually inherited from SimpleScalar; my > guess is that the only thing that might really get complicated if we > abandon that is register dependency handling in out-of-order models > (and maybe inorder too?). Before we take the step of getting rid of > that we may want to look at how we'd do those things otherwise. Or > perhaps the answer is that CPU models that want to incorporate a > merge() mapping are free to do so, but they must do it inside the > model and we won't assume it for any external interfaces. One thing we should remember is some ISAs have instructions that cross the register files domains. (e.g. move a float register to an int register or vise-versa). In those cases you definitely need dependence information between them for o3 execution.
Ali _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
