I'm not much into fasmg, but it seems to be a bug. fasmg has stopped being able to process single quotes as a part of a number.

While checking this I noticed another bug. fasmg is unable to process OS-specific paths correctly: in order to compile counter.asm in linux one needs to replace backslashes with forward slashes in the include argument.

Thanks for your reply.

FASMG.EXE also failed to compile :
;=============================
format ELF executable
entry start
segment readable executable
start: mov r0,0
add r1,pc,hello-$-8
mov r2,hello_len
swi 0x900004
mov r0,6
swi 0x900001
hello: db 'Hello world',10
hello_len=$-hello
segment writeable
;=============================

OK. I will try to implement some macroes to compile it by myself.

I still plan to try out my "stability counter" idea for an additional operator

Tomasz Grysztar

Quote:

I still plan to try out my "stability counter" idea for an additional operator

I don't think there's a necessity in a special operator. If I understand this correctly you want to provide an operator, which would bring up internal operation details of the assembler (multiple passes and value prediction/stabilization algorithms) to the interface instead of creating high-level rules that would persist independently on the ways the assembler finds the solution.

This is pretty much what I've been talking about in the topic you referenced, and what you subsequently elaborated by showing an extended condition to be satisfied by the assembler that guarantees no infinite oscillation. I see the problem as being just about finding a good high-level condition. It doesn't need explicit intra-pass specific checking and pass count control that you wanna legitimize by providing the additional special-purpose operator.

You may be right that any such feature would automatically be narrowing down the general concepts of fasm's language to specific implementation.

But as I'm not aware whether the floating point calculations of fasm g may actually be useful for anything other than basic purposes

You can also adjust the precision by altering the single constant in fasm g sources.

I implemented the BIT as EQU. But I wonder there must be a better way.

struc BIT? value
        define . value
end struc 

LED BIT P0.2

CLR LED    

struc BIT? value
        match any., value
                err "syntax error"
        else match base.index, value
                match any.other, base index
                        err "syntax error"
                else
                        define . base.index
                end match
        else match .any, value
                err "syntax error"
        else
                . = value
        end match
end struc 

LED BIT P0.2    

Tomasz Grysztar

Did you have some macros to compile MSP430/MSP432 in FASM ?

Tomasz Grysztar
I am. As you are bringing this up, I conclude, you are going to make the 1.0 release soon. So what's the deadline?