Yeah, sure. Lets say there's a conditional jump, and it needs to write the IP using the wrip microop. The exact condition you're testing will depend on *which* conditional jump it is, but they're all implemented using the same wrip microop which tests the condition codes and either writes a new IP value or doesn't. The set of conditions is different from the set of condition codes. If you want to look at how they map, check out the checkCondition function in src/arch/x86/insts/microop.cc
Gabe On 04/07/12 22:46, Steve Reinhardt wrote: > Hi Gabe, > > Thanks for all the info. For the most part this makes sense, but there's > one part I don't quite follow: > > The difficulty implementing this is that exactly which condition code >> bits to set and which to check for conditional microops are decided at >> the microcode level and are arbitrary combinations. > > I'm not quite sure what you mean by "conditional microops" here... can you > give a concrete example? > > Thanks, > > Steve > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
