home bbs files messages ]

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,686 of 4,675   
   wolfgang kern to R.Wieser   
   Re: Interpreting (the data following) a    
   04 Dec 18 19:50:57   
   
   From: nowhere@nospicedham.never.at   
      
   On 12/4/2018 6:47 PM, R.Wieser wrote:   
   ...   
   > [quote]   
   > D9 /6 FNSTENV* m14/28byte Store FPU environment to m14byte or m28byte   
   > without checking for pending unmasked floating-point exceptions. Then mask   
   > all floating-point exceptions.   
   > [/quote]   
      
   > I have abslutily *no* idea how to match it up with the 0x7E opcode folowing   
   > the INT 0x35.    The explanation for the "/6" is as follows:   
      
      
      
   > [quote]   
   > /digit-A digit between 0 and 7 indicates that the ModR/M byte of the   
   > instruction uses   
   > only the r/m (register or memory) operand.   
      
   the /6 in the RM-field (bits 3,4,5) and MOD 00 (bits 6,7) tells that   
   this opcode is FNSTENV   
      
   use_16:   
   D6 30     FNSTENV short [BX+SI]   
   66 D6 30  FNSTENV long  [BX+SI]   
      
   use_32:   
   66 D6 30  FNSTENV short [EAX]   
   D6 30     FNSTENV long  [EAX]   
      
   > The reg field contains the digit   
   > that provides an   
   > extension to the instruction's opcode.   
   > [/quote]   
      
   the reg-field (bits 0,1,2) is used for [mem only] addressing here.   
      
   where do you see an 0x7E "JMP NG" ?   
   __   
   wolfgang   
      
   --- 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