On 06/24/11 08:36, Nilay Vaish wrote: > On Sun, 26 Jun 2011, Gabe Black wrote: > >> >>> >>> Yes, that's correct. If it doesn't start with a 0x0F, there isn't any >>> way to tell if it's the start of a two byte opcode or just a one byte >>> opcode by itself. You might want to reconsider using an immediate, but >>> I wouldn't be -that- surprised if there was somewhere you could fit a >>> single opcode and get away with having an immediate. If I get a chance >>> I'll look for a spot, although I can't promise anything. >>> >>> Gabe >>> _______________________________________________ >>> gem5-users mailing list >>> [email protected] >>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> 0x0F 0x04 looks like it's available. It's marked as invalid which I >> assume means it's reserved in case they want to wedge more instructions >> in there, but it should be fine for you to use. My pdfs are a few years >> old so there may be some fancy new instruction that goes there, but you >> should be safe ignoring that. >> > > That's what we currently use for pseudo instructions. > > -- > Nilay > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Ok, 0x0F 0x36 which is right after sysexit. Gabe _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
