flat assembler 1.46 has just been released - generally no new features was added, only some small bugs were fixed and the includes for Win32 version were corrected a bit.

You can download it from the official website: http://fasm.sourceforge.net/.
If you have any trouble downloading from there, you can use the SourceForge releases system, it provides many mirrors. You can view the releases page for flat assembler here: https://sourceforge.net/project/showfiles.php?group_id=55941.

The technical documentation about the fasm sources is still far from being finished, but you can view what has been done yet here: http://fasm.sourceforge.net/fasmguide.txt.
Posted on 2003-04-09 11:36:53 by Tomasz Grysztar
Privalov,

Thanks for the 1.46:alright:

Regards,

Vortex
Posted on 2003-04-10 11:00:30 by Vortex
Thanks! But that link is not found
Posted on 2003-05-07 08:20:47 by fulmination
Which one doesn't work for you?
Posted on 2003-05-07 08:24:02 by Tomasz Grysztar
Both of them doesn't
Posted on 2003-05-08 00:00:28 by fulmination
That's strange. Does anybody else have some problems with accessing the SourceForge servers?
Posted on 2003-05-08 02:04:34 by Tomasz Grysztar
see if you can resolve fasm.sourcforge.net via ping fasm.sourceforge.net on a commandline (it should be 66.35.250.209)

if not place



66.35.250.209 fasm.sourceforge.net




in your "hosts" file

I hope it will help
Posted on 2003-05-08 05:51:58 by Hiroshimator
Hi Privalov,

No, I have not problems at all.

Regards
ipadilla
Posted on 2003-05-14 14:05:20 by ipadilla
from intel docs sal and shl must have the same opcode. /4
Posted on 2003-06-08 12:47:24 by octavio
valid floating point instructions whith st0,and a memory operand give this incorrect error message.
Posted on 2003-06-08 12:52:56 by octavio
Paste line.
Posted on 2003-06-08 16:52:49 by comrade
in 16bit mode the instruction 'jmp ecx' generates a bad opcode /5 (jmp mem) instead of /4 (jmp reg)
Posted on 2003-06-09 11:58:05 by octavio
Not allowed in 16-bit mode I guess...
Posted on 2003-06-09 18:38:08 by comrade

Not allowed in 16-bit mode I guess...

what about flat model?
Posted on 2003-06-10 11:55:48 by octavio

Not allowed in 16-bit mode I guess...

Yes it's allowed, but the hi-word must be clear before jmp.
this really is a bug.

use16
jmp eax

fasm produce 66 FF E8 instead of 66 FF E0
Posted on 2003-06-11 07:41:48 by quiveror

from intel docs sal and shl must have the same opcode. /4

Well, fasm has the support for some undocumented opcodes (also others like SALC/SETALC, LOADALL286, LOADALL386, old FPU instructions) and this is also the case. Howewer the best is just to use SHL all the time - according to the intel docs SAL is just the synonym for it (you can put "sal equ shl" at the beginning of your sources if you have it to be generated the "official" way).
Posted on 2003-06-12 03:57:40 by Tomasz Grysztar


Yes it's allowed, but the hi-word must be clear before jmp.
this really is a bug.

use16
jmp eax

fasm produce 66 FF E8 instead of 66 FF E0

No, it's not a bug - in 16-bit mode fasm generates dword jumps as the far jumps by default, if you want to have 66 FF E0 opcode, use "jmp near eax".

octavio: What floating point instructions did you mean?
Posted on 2003-06-12 04:02:24 by Tomasz Grysztar


No, it's not a bug - in 16-bit mode fasm generates dword jumps as the far jumps by default, if you want to have 66 FF E0 opcode, use "jmp near eax".


The problem is that 66 FF E8 isn't a valid opcode for x86. It will always generate exception 6 (invalid opcode). Opcode FF /5 doesn't accept registers as its operand. I think FASM should produce an error message instead of generate an invalid opcode? :rolleyes:

regard,
Posted on 2003-06-12 16:10:52 by quiveror
Strange, I thought it was working for me somewhere - probably I had some wild processor. Will check it again...
Posted on 2003-06-12 18:04:14 by Tomasz Grysztar


No, it's not a bug - in 16-bit mode fasm generates dword jumps as the far jumps by default, if you want to have 66 FF E0 opcode, use "jmp near eax".

octavio: What floating point instructions did you mean?

fadd st0,dword and similar instructions
I know you can write fadd dword, is just a sintax problem.
Posted on 2003-06-13 11:37:17 by octavio