flat assembler
Message board for the users of flat assembler.
Index
> Compiler Internals > lock prefix freedom |
Author |
|
ouadji 23 Jun 2011, 14:56
#UD Invalid Opcode Exception |
|||
23 Jun 2011, 14:56 |
|
JoeCoder1 23 Jun 2011, 17:10
haha isn't lock interpreted as a label there
|
|||
23 Jun 2011, 17:10 |
|
bitshifter 24 Jun 2011, 00:58
No, its a prefix, like rep is also a prefix
Code: repe stos byte[edi] A lock label would be like Code: _lock: lock mul bx Now the real question is: Should FASM be allowed to generate invalid opcodes? |
|||
24 Jun 2011, 00:58 |
|
revolution 28 Jun 2011, 03:49
bitshifter wrote: Should FASM be allowed to generate invalid opcodes? I even have some old 80286 boards that used the hardware lock signal for some special purposes other than locking memory accesses. Subsequently the code had some lock's in places that looked very weird until one realised that it was simply raising an external signal and not controlling any memory functionality. |
|||
28 Jun 2011, 03:49 |
|
Madis731 28 Jun 2011, 06:07
Code: cs gs lock repe mul bx Sometimes it just HAS to make sense Its an oldie, but I couldn't resist Code: who | grep -i blonde | talk ; cd ~; wine; talk; touch; unzip; touch; strip; gasp; finger; gasp; mount; fsck; more; yes; gasp; umount; make clean; sleep Last edited by Madis731 on 28 Jun 2011, 06:16; edited 1 time in total |
|||
28 Jun 2011, 06:07 |
|
revolution 28 Jun 2011, 06:11
Madis731: Also ...
Code: gs fs es ss cs ds lock rep lea eax,ebx https://board.flatassembler.net/~flatasse/subdomains/board/topic.php?p=65787#65787 |
|||
28 Jun 2011, 06:11 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2025, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.