flat assembler
Message board for the users of flat assembler.
Index
> Compiler Internals > About FSAVE encoding |
Author |
|
hopcode 16 Jan 2010, 11:54
After reading this,
http://board.flatassembler.net/topic.php?t=5287 i find it ok the reason, because of Fasm basic data types as definded in the manual. For FSAVE, for example Code: super_data db 94 dup (0) ; or 108 super_pointer: db 94 dup (0) FSAVE [super_pointer] ;ok FSAVE [super_data] ;err invalid operand but,as you know,for example, Code: FSAVE [EAX] ;ok FSAVE [EBP*4+EAX] ;ok ; ... etc... ok because,actually, after having been opcoded, all of the (16/32) 256 type of MOD/RM could be used,(excluded MOD=11 i guess) depending only on the actual operand size So, i had been thinking for a while..., why not simply Code: FSAVE super_data it is to say, avoiding type-checking in the declaration of super_data, because it is always implicitly depending on the operand size 66 or not 66 ? Greetings, hopcode |
|||
16 Jan 2010, 11:54 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.