Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,684 of 4,675    |
|    R.Wieser to All    |
|    Re: Interpreting (the data following) a     |
|    04 Dec 18 21:04:57    |
   
   From: address@nospicedham.not.available   
      
   Rick,   
      
   > The Mod/Reg/RM byte is a traditional encoding byte in all   
   > of x86 assembly, and it's not specific to FPU operations or   
   > anything else specific.   
      
   I know how it works for the x86 comands. For the FPU commands ? No so   
   much.   
      
   Even if I read the explanation to that "/{digit}" wrong and it doesn't   
   implicitily exclude the "Mod" part from consideration, than I'm still left   
   with the "Reg" part (which refers to a register), which has no meaning for   
   most FPU commands (with the exclusion of one or two none use a register as   
   source *or* target).   
      
   If I use both the "Mod" as well as the "RM" parts the INT 0x35, 0x7E 0xFA   
   sequence decodes to :   
      
   FNSTENV [BP-0x06]   
      
   , which looks sensible to me.   
      
   But that stil leaves the "Reg" part, which for th 0x7E value refers to the   
   DI register. Which does not mean anything to me.   
      
   So, what *does* it mean ?   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca