flat assembler
Message board for the users of flat assembler.
![]() Goto page Previous 1, 2 |
Author |
|
Hunter
Tomasz, Why don't you want to support muti-byte NOP for completeness?
![]() |
|||
![]() |
|
Madis731
Hmm, but how would it be implemented then?
Code: nop word nop dword nop ![]() |
|||
![]() |
|
vid
if, then "nop word", not otherwise
![]() |
|||
![]() |
|
Tomasz Grysztar
The syntax like "nop dword [eax]" appears obvious from the opcode point of view, though its usability is questionable. Perhaps the syntax where you could directly specify how many bytes long NOP you want would be better, but for this I'd stick to macro solution (we can make a package of code alignment macros for different processors).
|
|||
![]() |
|
vid
i also like the idea with macros more... anyway, it's still just optimization, all those instructions are encodeable using current assembler
|
|||
![]() |
|
LocoDelAssembly
My Athlon64 reaches int3 with this
Code: format PE GUI 4.0 macro nop src { local ..lea if ~src eq db $0F ..lea: lea eax, src store $1F at ..lea else nop end if } irps instr, noP nOp nOP Nop NoP NOp NOP {macro instr src \{nop src\}} nop dword [ebx+esi+5] int3 |
|||
![]() |
|
Hunter
I think, It's needed for completeness, because it's official Intel instruction and official mnemocode.
![]() |
|||
![]() |
|
MazeGen
vid wrote: same way like some guy patented a wheel after law change in astrualia... Sorry for off-topic, I couldn't resist. Friend of mine has found the link: http://news.bbc.co.uk/2/hi/asia-pacific/1418165.stm |
|||
![]() |
|
Goto page Previous 1, 2 < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.