fasmg: Mix arm64 with x86

Yes, it's possible with help of namespace separation:

Code:

include 'win32ax.inc'

define ARM64
namespace ARM64
    include 'cpu/aarch64.inc'
end namespace

.code

; ---------------------------
; This function is in x86
; ---------------------------
MyFunction:
    mov     eax, 1
    ret

namespace ARM64
    ; ---------------------------
    ; This function is in ARM64
    ; ---------------------------
    MyFunction:
        ret
end namespace

; Back to x86. Here access the function as ARM64.MyFunction

start:
    invoke  ExitProcess,0

.end start

This is a "weak" separation, any x86 instructions that are not overridden by ARM64 ones are still visible in the embedded namespace, and the architectures may interfere with each other.

For a clean solution, you could make it a strong isolation:

Code:

; In the main namespace, define only PE format structures, with no specific CPU instructions:
PE.Settings.Characteristics = IMAGE_FILE_EXECUTABLE_IMAGE or IMAGE_FILE_32BIT_MACHINE or IMAGE_FILE_LINE_NUMS_STRIPPED or IMAGE_FILE_LOCAL_SYMS_STRIPPED
PE.Settings.Subsystem = IMAGE_SUBSYSTEM_WINDOWS_GUI
format binary as 'exe'
include 'format/pe.inc'

; When PE.INC was included manually, WIN32AX.INC does not do it itself:
include 'win32ax.inc'

; Define global anchors for the namespaces:
define X86
define ARM64

; Put instruction sets into separated namespaces. Now they cannot interfere with each other.
namespace X86
    include 'cpu/80386.inc'
    use32
end namespace

namespace ARM64
    include 'cpu/aarch64.inc'
end namespace

.code

namespace X86
    ; ---------------------------
    ; This function is in x86
    ; ---------------------------
    MyFunction:
        mov     eax, 1
        ret
end namespace

namespace ARM64
    ; ---------------------------
    ; This function is in ARM64
    ; ---------------------------
    MyFunction:
        ret
end namespace

namespace X86

    start:
        invoke  ExitProcess,0

end namespace

.end X86.start

This is in fact a perfect demonstration of the intended purpose of fasmg's namespaces.

To confirm correctness you can include 'listing.inc' (put it after the ".code" line to avoid processing all the headers). I got:

Code:

[0000000000401000]                                    namespace X86
[0000000000401000]                                    MyFunction:
[0000000000401000] 00000200: B8 01 00 00 00           mov eax, 1
[0000000000401005] 00000205: C3                       ret
[0000000000401006]                                    namespace ARM64
[0000000000401006]                                    MyFunction:
[0000000000401006] 00000206: C0 03 5F D6              ret
[000000000040100A]                                    namespace X86
[000000000040100A]                                    start:
[000000000040100A] 0000020A: 6A 00 FF 15 40 20 40 00  invoke ExitProcess,0

You can also mix different flavors of x86 in the exact same way.