Source

Thread

1/ @NOTimothyLottes

All {0-6} argument syscall options in 32-bytes. The plan is to embed the interpreter inside the words with a 3-byte overhead {AD (lodsd), FF E0 (jmp rax)} so levering lots of x86-64 stuff for minimal size

2/ @NOTimothyLottes

Everything forced in lower 32-bit, but still building around 64-bit support. Since I’m not using x86-64 CALL/RET I can free up the stack ops strictly for the data stack.

3/ @NOTimothyLottes

I realized at some point I can have most interpreted forth-style words in an aligned 8-bytes. So can make a very small interpreter.

Branches: 2026-07-18-noop_dev-even-smaller-code-size-possible-with-custom

0 items under this folder.