-
Only matters for reference types. But if we know the call is borrowing a reference type that will outlive the call, we don't need to add it into the activations table because the borrow checker alread…
-
See if we can compile to WASI the cli context functions, and them to be WASI functions that access STDIO and FS etc?
If we can, then they could be moved to a library and not in the runtime and the ru…
-
The implementation of "command" modules in `Linker` will create a new `Instance` each time an export is invoked. This works well implementation-wise but it's also easy to leak memory and resources uni…
-
## Description
I have generated a wasm binary which with no WASI function. And I processed it with Wasmedge and the other runtimes, such as wasmtime and wasmer, while WasmEdge is much slower than the…
-
| | |
|--------------------|----|
| Bugzilla Link | [PR50413](https://bugs.llvm.org/show_bug.cgi?id=50413) |
| Status | NEW |
| Importance | P enhancemen…
-
Currently neither LLVM nor Cranelift implement stack probing on AArch64, which means that malicious Wasm code could potentially write to memory past the end of the stack.
Related:
- Rust issue: ht…
-
Problem:
TinyGo Spin apps that use `log` gets the following runtime error from Wasmtime:
```sh
$ spin build --up
Building component go-app with `tinygo build -target=wasi -gc=leaking -no-debug -…
-
These seem to be available in the rust api but there doesn't seem to be an equivalent in the C api. They would be useful for the Perl bindings that I am working on.
-
I get a `Insufficient resources: System call failed: Cannot allocate memory (os error 12)'` error when trying to spawn too many processes. The processes are almost empty - just a single sleep instruct…
-
Is there a way to get the equivalent behavior of `docker run -it`, for example if I wanted to run the docker/doodle containers: https://hub.docker.com/r/docker/doodle/tags