←back to thread

38 points frou_dh | 2 comments | | HN request time: 0.683s | source
Show context
dartos ◴[] No.42480429[source]
A friend of mine worked on https://github.com/libriscv/godot-sandbox

Which uses libriscv as the sandboxed compute target.

IIRC They tried for years to get a wasm backend to work and eventually abandoned it citing, among other reasons, something about how it was difficult to wrangle a stack machine with a register machine.

I don’t really see what benefits wasm runtimes have over something like libriscv which is very fast and maps more closely to hardware.

replies(3): >>42480859 #>>42481522 #>>42482334 #
1. apitman ◴[] No.42480859[source]
First I've heard of libriscv. What exactly is it? A wasm alternative that uses RISCV byte code?
replies(1): >>42484904 #
2. dartos ◴[] No.42484904[source]
Wasm and risc-v are totally different.

Wasm is an assembly like language for high performance computing in the browser

And risc-v is an arm-like instruction set for physical CPUs.

Wasm has a lot of runtimes which are basically VMs that run wasm.

Libriscv is a very small very vast VM that runs riscv assembly.