wasmtime icon indicating copy to clipboard operation
wasmtime copied to clipboard

A fast and secure runtime for WebAssembly

Results 758 wasmtime issues
Sort by recently updated
recently updated
newest added

Currently, `s390x` is the only big-endian platform supported by cranelift, which has already caused problems related to memory accesses in the past, since wasmtime defines all data in its memory...

cranelift
cranelift:discussion
cranelift:area:clif

I'm opening this as a loose tracking issue for removing the need to have inline assembly trampolines defined by Wasmtime. Ideally all trampolines necessary could be provided by Cranelift instead...

wasmtime

#### Feature Rust library can bind WritePipe to WasiCtx stdout which can be far simpler and effective than OS files went dealing with multiple short-lived instances. It is not currently...

wasmtime:c-api

Thanks for filing an issue! Please fill out the TODOs below. ### `.clif` Test Case ``` function u0:0() -> i64 apple_aarch64 { sig0 = (i64) -> i64 apple_aarch64 sig1 =...

bug
cranelift

* This has been discussed in issue #4610. * Update `wasi-crypto` * Test Wasm https://github.com/rjzak/wasi-crypto-example/releases/tag/v0.0.1 CC: @npmccallum, @sunfishcode

This is a meta issue to track the migration from hand-written instruction selection and lowering over to using the ISLE DSL. As you port lowering for a clif opcode over...

cranelift
cranelift:E-compiler
cranelift:area:aarch64
cranelift:area:x64
isle
cranelift:area:s390x

On Mac aarch64 (e.g. M1 MBP), the system's libunwind doesn't behave as on other platforms, and doesn't properly unwind wasm frames using the information we provide it (CFI etc.). The...

bug

`wasi-crypto` has seen some changes recently, and `wasmtime-wasi-crypto` is missing a function. Some of the guest types have also changes. Can we have an update to pull in the latest...

Currently the `Linker::func_new` API added in https://github.com/bytecodealliance/wasmtime/pull/4537 has a bit of an odd API for the creation of a host function. Instead of taking a `Component`/string pair this should ideally...

wasm-proposal:component-model

Similar to `Module::{imports,exports}` it should be possible to call `Component::{imports,exports}` and inspect, at runtime, the types used within a component.

wasm-proposal:component-model