Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Lil VM assembly output and documentation

A topic by oschettler created Apr 06, 2025 Views: 220 Replies: 2
Viewing posts 1 to 3
(-1)

I am fascinated to be able to run Decker as a kind of operating system on some microcontroller-driven display-board in the future.

To better understand how the VM in c/lil.h works. I‘ve added an option to output „assembly code“ by passing „-s“ as a command line option to lilt: https://github.com/JohnEarnest/Decker/pull/11

Based on this, I have asked a friendly LLM to write me some documentation on the VM: https://github.com/codekulturbonn/Decker/blob/main/docs/vm.md

Developer(+4)

Decker is a program written by and for humans. If you want help understanding some aspect of it, feel free to ask. I have no interest in source code or documentation generated by LLMs; fact-checking the results of a black-box machine learning model is a very unappealing way to spend my time.

Lil's internal bytecode is not intended as a stable contract; from time to time I make changes or introduce new opcodes. I'd prefer not to ossify the design and increase my maintenance burden by making it a documented public interface. You are welcome to explore such experiments in your own fork, but I don't think this idea is appropriate for mainline Decker.

(+3)

Hi, apologies for creating this pull request and I certainly understand your position, both with respect to LLMs in general and not wanting to freeze the VM. So, thank you again for this lovely piece of software and the chance to play with and learn from it.