flat assembler
Message board for the users of flat assembler.
Index
> Main > Multi-byte NOP instructions support Goto page 1, 2 Next |
Author |
|
vid 10 Jul 2006, 18:30
there was already thread about this i think. try searching before posting
|
|||
10 Jul 2006, 18:30 |
|
LocoDelAssembly 10 Jul 2006, 21:08
Can you post the thread where it appears? All what I found about NOP is not related to this.
|
|||
10 Jul 2006, 21:08 |
|
Hunter 11 Jul 2006, 10:31
I also not found any related topics.
Tomasz, what do you think about this problem? |
|||
11 Jul 2006, 10:31 |
|
Tomasz Grysztar 11 Jul 2006, 14:57
Perphaps vid this means threads like this: http://board.flatassembler.net/topic.php?p=23957#23957 ?
|
|||
11 Jul 2006, 14:57 |
|
vid 11 Jul 2006, 16:45
yup - you meant something else? (sorry, i don't have those manuals..)
|
|||
11 Jul 2006, 16:45 |
|
Hunter 11 Jul 2006, 16:57
Tomasz, I've seen this link, but there are another opcodes.
NOP r/m16 ; 0F 1F /0 NOP r/m32 ; 0F 1F /0 it's official opcode from Intel manual. |
|||
11 Jul 2006, 16:57 |
|
LocoDelAssembly 11 Jul 2006, 18:55
I tested the opcodes of that manual on my Athlon64 and no invalid opcode exception was generated
OllyDbg does not recognizes them though |
|||
11 Jul 2006, 18:55 |
|
vid 11 Jul 2006, 20:18
does it touch memory region, or what is it for? just faster padding?
|
|||
11 Jul 2006, 20:18 |
|
mattst88 11 Jul 2006, 20:35
|
|||
11 Jul 2006, 20:35 |
|
LocoDelAssembly 11 Jul 2006, 22:05
Here it is what Hunter is telling:
|
|||
11 Jul 2006, 22:05 |
|
LocoDelAssembly 11 Jul 2006, 22:38
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\}} db $66 NOP NOP DWORD [EAX] ; Due to the optimization of FASM, 00H byte displacement will not be encoded NOP DWORD [EAX + 01H] NOP DWORD [EAX + EAX*1 + 01H] db $66 NOP DWORD [EAX + EAX*1 + 01H] NOP DWORD [dword EAX + 00000000H] NOP DWORD [dword EAX + EAX*1 + 00000000H] db $66 NOP DWORD [dword EAX + EAX*1 + 00000000H] int3 At least on my CPU reaches int3 without problems. |
|||
11 Jul 2006, 22:38 |
|
Tomasz Grysztar 12 Jul 2006, 07:14
66 90 is "XCHG AX,AX"
|
|||
12 Jul 2006, 07:14 |
|
Hunter 12 Jul 2006, 09:59
Ok, Tomasz, could you add muti-byte NOP support to FASM?
|
|||
12 Jul 2006, 09:59 |
|
RedGhost 12 Jul 2006, 12:08
hmm, $60 $90 is infact xchg ax, ax
xchg eax, eax generations $90, i did not know this, xchg ebx, ebx or related would be 2 bytes but xchg eax, eax is 1 learn something new everyday _________________ redghost.ca |
|||
12 Jul 2006, 12:08 |
|
LocoDelAssembly 12 Jul 2006, 13:29
|
|||
12 Jul 2006, 13:29 |
|
Reverend 14 Jul 2006, 10:16
RedGhost: All "xchg eax, xxx" are one-byte long. That's true for all xchgs with eax as operand. Other variations are two-byte long
|
|||
14 Jul 2006, 10:16 |
|
MazeGen 24 Jul 2006, 07:51
See also U.S. Patent 5,701,442. It covers opcodes 0F18-0F1F.
|
|||
24 Jul 2006, 07:51 |
|
vid 24 Jul 2006, 08:15
MazeGen wrote: See also U.S. Patent 5,701,442. It covers opcodes 0F18-0F1F. That USA crap is terrible? How can you people live there?!? |
|||
24 Jul 2006, 08:15 |
|
UCM 24 Jul 2006, 13:26
vid: no kidding.
How can you patent an instruction? |
|||
24 Jul 2006, 13:26 |
|
Goto page 1, 2 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2025, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.