4984

6 ms·

1.
by 4984 4y ago
The benchmarks were run on MacOS, and actually execute an interrupt for debugging, MacOS then checks if the process is being debugged. Wasm3 just exit(1) and prints a message. And as to why the rest are faster, I spent much time optimizing
2.
by 4984 4y ago
I made Web49 because there are not many good tools for WebAssembly out there. WABT is close, but the interpreter is too slow and the tools megabytes in size each. Wasm3 is a bit faster but only contains an interpreter, nothing else. Tooling
3.
Show HN: I wrote a WebAssembly Interpreter and Toolkit in C(github.com)
105 points by 4984 4y ago|28 comments
4.
by 4984 4y ago
The interview in question, for those interested: https://odin-lang.org/news/newsletter-2022-12/#interview-wit...
5.
by 4984 5y ago
I have looked into Meta Machines. They are not what I want. Meta Machines can be almost as fast, but i just prefer the cache locality of local functions. Wasm3 is slower than MiniVM when you don't count the GC. Wasm3 is very cool!
6.
by 4984 5y ago
There is no roadmap. There are no written long term goals. This project came out of need for a faster virtual machine for my Paka language. There is an api to emit vm bytecode, but it's not in C, it is from Paka. Roadmap could go like
7.
by 4984 5y ago
MiniVM uses coroutines already, every 1000 branches the vm will return to the scheduler. The Build system can accept CFLAGS+=-DVM_BRANCH_DEFER which makes MiniVM able to run part of bytecode up-to N instructions. It is not exposed on the in
8.
by 4984 5y ago
Author here, Tail calls can be implemented in MiniVM bytecode. There was once an instruction that performed a tail call, It bit-rotted due to not being used. MiniVM is moving very quickly currently. A lot still needs to be done, like JIT an
9.
by 4984 5y ago
Thank you for having a look. The reason MiniVM is so benchmark-oriented in its presentation is that MiniVM is ver benchmark-oriented in my workflow. I have tried to find a faster interpreter without JIT. It is hard to find benchmarks that d
10.
by 4984 5y ago
MiniVM will JIT eventually. Right now the biggest barrier is the VM snapshots. Currently MiniVM its own stack and heap and can snapshot them from any point in the program. One thing to note about MiniVM is that it has very strong types. V8