fasm 2 as a set of scripts and headers for fasmg

include 'win64w.inc' format pe64 struct Test2 a1 rd 1 ends struct Test3 a1 rd 1 a2 rd 1 a3 rd 1 a4 rd 1 a5 rd 1 ends struct Test1 a1 rd 1 a2 Test2 a3 Test3 ends struct Test4 a1 rd 1 a2 rd 1 ends virtual at 0 V1 Test4 V2 Test4 end virtual mov esi,[rax+rax+Test1.a3+V1.a1] ret

vityacv wrote:

Having issue with this sample on FASM 2 - Custom error: operand sizes do not match.

Code:

include 'win64w.inc'
format pe64

struct Test2
a1 rd 1
ends

struct Test3
a1 rd 1
a2 rd 1
a3 rd 1
a4 rd 1
a5 rd 1
ends

struct Test1
a1 rd 1
a2 Test2
a3 Test3
ends

struct Test4
a1 rd 1
a2 rd 1
ends

virtual at 0
V1 Test4
V2 Test4
end virtual

mov esi,[rax+rax+Test1.a3+V1.a1]
ret

FASM 1 compiles without error

The "Test1.a3" has associated size (20 bytes), as the STRUCT macro in fasm2 has an added feature of sizing all these labels properly. This was missing in fasm's implementation, because it was not really possible to implement there except for a small set of supported sizes.

If you'd prefer to not have this feature, comment out the portion of "instantiate" macro:

Code:

                arrange tmp, =label instance; : sname.=__size__

Another workaround is to rearrange the expression so that the intended size comes first.