bytecodealliance / bytecodealliance/javy
Support a WASI reactor target
Open
enhancement
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 135
- Avg merge
- 1d 44m
- Merged PRs (30d)
- 11
Description
Operating system: macOS
Processor architecture: M1 (arm64)
Rust version: not applicable
Javy version: latest
## Problem
WASI/WASM ceremony is all over the place depending on what compiler produced the module. Most expect _start or _initialize to be called prior to any exported functions being invoked.
In the case of modules produced by Javy, if _start is called any subsequent calls to exported functions will fail with wasmtime reporting they’re unreachable.
If I remove my calls to _start then I can call into my exported functions without issue.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.