fasm dont compile code like this ("invalid use of symbol"):

why?

It works for me.
Maybe you should post bigger snippet from your code.

Regards.

may be, you write

i'm use fasmw 1.50, and "jmp dword 0" not work.

It works, but perhaps you are using PE output format, which is a relocatable format by default. In case of relocatable formats such instruction cannot be encoded correctly, so fasm generates an error. You may also find this thread helpful in that case, there is a solution for this problem based on assumption, that you won't include relocations in your PE file.

And if you are creating one of the object formats, like COFF or ELF, you cannot make such instructions at all, because those formats have to be relocatable in any case.

Well, you can see the version, source and the result:

Thanks!

Wouldn't it be better to detect if you have defined a relocation section (in PE format), and if not, generate the code correctly?

The only solution would be to restart the assembly completely with new settings when the relocation section is detected (and then it still would fail, as it may happen that someone is putting fixups inside the conditional blocks and the conditions changes between those passes). Perhaps it's possible, but would need some huge changes in PE formatter - I'm not sure whether macro solution is not just a simpler one.

And, BTW, in general you shouldn't use such insctructions in PE format, and you should include relocations, even though non-relocatable PE programs used to work on most of the Win32 systems (AFAIK, except for the Win32s).

Ok...
Then, how about adding a nonrelocatable flag that you can use with the format directive (at least for PE format)?

I'm not sure how much changes would it require, as I don't know the FAsm code that well... not too much I guess, just ignore the fixups when the flag is set.

Anyway it's not a very large issue, and you can use macros to get around it, so...

Hi Priv. Are you saying that, under Win32s, PE.exe(s) require Reloc?

If yes, where did you got the info from, and (... excuse me, but i don't know of it...) is there another name for "Win32s". What OS flavour is this?


Betov.

Betov: No, relocations are not required for PE executable, but if the system is not able to load program at its default address, it needs relocations to execute it, and such program just won't work if it doesn't include relocations. So it is much safer to generate PE with relocations, and earlier fasm version were even generating .reloc section automatically even if it hadn't been declared in source.
And Win32s is the overlay for Windows 3.11 that allowed to run Win32 programs (those were WinNT programs only those days) on that system. Perhaps it was also a base for later kernels of Win95/98/Me series, but since Win95 it was capable of loading every program at default base 400000h, while Win32s wasn't.

AMD64: Yes, that would be a solution, but since the same thing can be easily achieved with macros, I don't consider it really worth the effort. But if it happens to me that I can add such feature on the occasion of some other formatter changes, I'll do it.