On Sat, Dec 22, 2012 at 8:44 PM, Gleb Natapov <gleb@xxxxxxxxxx> wrote: > On Sat, Dec 22, 2012 at 08:18:14PM +0200, Avi Kivity wrote: >> > No, I was just truing to make sure I am not missing something :) >> > Wouldn't we have to have separate fastop() function to handle rax/rdx >> > output instructions? >> >> No. As long as fastop() sets up and writes back rdx correctly (and >> also #DE for DIV, IDIV), a single implementation works for everything. >> I don't want to add even more layers of indirect dispatch. > > OK, so fastop() will always writeback RDX and handle exceptions, or you > want to mark instructions that needs this special handling with yet > another flag? Hopefully completely unconditional, but we'll see. The problem is that if we pass rdx and another output parameter for exceptions, we run out of registers on i386. We can probably hack our way though. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
