I think that fasm has a bug that makes impossible to assemble control transfers instructions that make use of relative addresing

I tried to compile a little test code that uses elf format and use16
but it produces error



Error Message:

test.asm [13]:
call atoi
error: invalid use of symbol.

I ported this code to nasm and it compiles fine to elf format, then I linked it with ld to output binary and I checked the opcodes and the displacement value of the call instruction and it's fine in the binary output file, the elf format worked with 16 bit code

This is actually the same thing that was discussed here: http://board.flatassembler.net/topic.php?t=5703

I have found how to fix this issue hopefully, declaring 'org $0' inside the text section, so it compiles fine now

However this way you disable the relocations. And if you don't need the relocations, why not use direct binary output instead of object?

becuase binary format in fasm doesn't allow me the use of sections, I think that nasm was able of this, I need to keep the code and data isolated in format binary, without matterring in which place of the source they are declared, as I'm trying to keep my sources in modules and each source module has code and data.

I think he means using "format elf executable" (which allows the use of sections too).

So you link the few objects, each with code and data section into one? The you won't be able to cross-reference the code and data between different files if you disable the relocations.

well, so then I think that the best solution is that I need a way for put all declared data in a position ahead of all code, without mattering the place where the data is declared using format binary directive.

The idea of flat binary formatter is that the structure and order of the source exactly reflects the structure and order of the resulting file. This is a kind of WYSIWYG applied to assembly.