• vulkasm
  • Synopsis:
  • Dependencies:
  • APIs:
  • Build:
  • Features:
  • Description:
    • Libraries:
    • MASM64 SDK:
    • Vulkan:
    • Code Style:
      • Build Style:
      • Calling Convention:
      • Modular Assembler Style:
  • Todo:
  • Miscellaneous:
  • CheatSheet:
    • Registers:
    • Volatile vs Non-Volatile
    • Learning Resources:

Pure x64 Microsoft Macro Assembler & Vulkan Game Engine to explore Assembly Programming.

• Visual Studio 2022 for ml64.exe & link.exe
• Vulkan SDK 1.4.313.0 for the vulkan-1.lib

• Unofficial MASM64 SDK .asm found in extern\masm64
• Assembler compatible Vulkan headers found in extern\vulkan

• Launch x64 Native Tools Command Prompt for VS 2022
• Run scripts\build.bat
• Run build\main.exe or devenv build\main.exe

• MASM64 based Arena Allocator (saha.asm)
• Translated Vulkan C headers to MASM64 (using tools\vulkan_gen.bat)

Not using the CRT at all, just pure Assembler + Win32 + Vulkan.

I don't need the full SDK so I just took the .asm files and placed them in my project.
They are hard coded to be in the C:\ root so maybe this can be fixed later.

I'm using 1.4.313.0 but it should be upgradable using vulkan-extractor.py.

I went ahead and made a Unity/Jumbo build:

• Everything is included inside main.asm
• Only assembing main.asm is required
• Modules have header guards
• Modules are used to fake private but everything is global
• Variables/Functions dumped in main are intended to be specifically global

• The MASM64 SDK comes with an invoke macro that automates the Windows x64 calling convention
• Example: void Proc(&handle, count, NULL); -> invoke Proc, ADDR handle, count, 0
• In case of stack usage, stack MUST be aligned to 0x10 or 16 so make sure RSP ends with a 0 before calling a Windows or Vulkan function.
• I noticed that the invoke macro doesn't take care of the shadow space allocation so you have to sub rsp, 32 then add rsp, 32 before a function call or else crash. This is especially true if you have to call some Windows/Vulkan function multiple times in a row such as printing otherwise its fine.

• I divided each vulkan step into its own module with each module having its own variables as I did not do any stack allocation.
• Modules look like this: ModuleDrawFrame.asm and inside DrawFrame_render_info for vars and DrawFrame_Execute for procs.
• Everything is zeroed out since everything is allocated in the .data section but I don't zero anything manually which might be dangerous.
• Look at ModuleTemplate.asm

• Get the Vulkan triangle
• Fix saha.asm arena macro
• Create an arena allocator for permanent storage
• Create modules for the rest of the vulkan code
• Clean up vulkan-extractor.py
• Play with SIMD and game logic

You can regenerate the vulkan headers using python + libclang by invoking the ugly vulkan_gen.bat file from the tools directory. The generated headers are almost perfect except for a few bugs which I fixed manually. Will fully automate the process.

If you are new to x86-64 Assembly I suggest:

• masm64-init
• The Art of 64-Bit Assembly, Volume 1: x86-64 Machine Organization and Programming
• Assembly x64 Programming in easy steps