wizer
wizer copied to clipboard
The WebAssembly Pre-Initializer
This is probably useful to add. https://docs.rs/wasm-metadata/0.206.0/wasm_metadata/struct.Producers.html https://github.com/WebAssembly/tool-conventions/blob/main/ProducersSection.md
Hi when I want to install @fastly/js-compute on Alpine Linux, it says wizer not found! ``` yarn build:app > js-compute-runtime app/index.js /app/node_modules/@bytecodealliance/wizer-linux-x64/wizer: not found Error: Failed to compile JavaScript to...
I have a WASM module that uses reference types, but the initialization function (some pure precomputation) doesn't use them. Currently, wizer categorically fails with ``` Error: reference types support is...
``` error[E0599]: no associated item named `FIXED` found for struct `MapFlags` in the current scope --> /usr/ports/devel/wizer/work/wizer-1.6.0/cargo-crates/wasmtime-runtime-0.35.3/src/instance/allocator/pooling/unix.rs:21:67 | 21 | rustix::io::MapFlags::PRIVATE | rustix::io::MapFlags::FIXED, | ^^^^^ associated item not found in...
As of WASI SDK 16, `__original_main` is no longer added, breaking this: https://github.com/bytecodealliance/wizer/blob/65e345fb2bd5b5177d4be55af747edc28035c35c/include/wizer.h#L87-L90 https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-16 I am not sure what issue #295 is referring to there.
Right now, you can either turn WASI on or off. But there is no reason a user of the builder API shouldn't be able to provide their own `wasmtime::Linker` that...
https://github.com/WebAssembly/component-model This will require using interface types for the initialization function. Not 100% clear whether we want to keep the same init function interface (no params and no returns) or...
There are concerns with the emscripten Godot project that the snapshot will increase bandwidth usage too much. (emscripten support is a separate issue) For the subset of programs that: 1....
Right now there are two potential kinds of tables: * `funcref` tables * `externref` tables The latter are easy to support, since Wasm can't construct an `externref`, only receive it...
When using Wizer as part of a build process, it's not always desirable to have the Wasm backtrace dumped if the guest code didn't exit successfully. Would anything speak against...