Reuben Dunnington
Reuben Dunnington
The wrapper function was mistakenly referencing ntdll.zig when the actual function is declared in kernel32.zig.
Closes #27 * Adds support for the `memory64` spec proposal. `table64` support will be upcoming when clang adds support for it. * New overridable logging interface (exposure via FFI TODO)...
`zig build test-cffi` should build a C file that loads a wasm file and invokes a function in it, link it with `bytebox.lib`, and run the exe, expecting no errors....
Stack-based VMs have inherent performance limitations that are not present in register-based VMs. To reach or surpass performance of other WASM interpreters, bytebox will need to implement a register-based VM....
* Official spec seems to be here: https://github.com/WebAssembly/memory64 * Needed to support Orca's desired memory model
As of this writing, wasi-testsuite does not have full coverage of the functions in preview1, and as a result the untested functions have not been implemented. To reach parity with...
Currently the order of args is: `bytebox [WASM_ARGS]... [OPTION]...`. However, wasmtime (and other runtimes) put their option args before the wasm file like so: `wasmtime [OPTION]... [WASM_ARGS]...`. Bytebox should match...
The current implementation of the wasi functions are not threadsafe, as wasi file descriptors are backed by an internal data structure that isn't threadsafe, nor wrapped by any locks. This...
Currently the wasi_rights arg is essentially ignored for most wasi calls. To be compliant with the spec, the bytebox wasi runtime should return NOTCAPABLE when functions are called for file...
### Zig Version 0.12.0 ### Steps to Reproduce and Observed Behavior With this program `memtest.zig`: ```zig const KB = 1024; const MB = 1024 * KB; const GB = 1024...