Update wasmtime to 0.27 (#8913)
* Update wasmtime to 0.27 A couple of notes: - Now we are fair about unsafeness of runtime creation via an compiled artifact. This change was prompted by the change in wasmtime which made `deserialize` rightfully unsafe. Now `CodeSupplyMode` was hidden and the `create_runtime` now takes the blob again and there is now a new fn for creating a runtime with a compiled artifact. - This is a big change for wasmtime. They switched to the modern backend for code generation. While this can bring performance improvements, it can also introduce some problems. In fact, 0.27 fixed a serious issue that could lead to sandbox escape. Hence we need a proper burn in. This would require a change to PVF validation host as well. * Filter regalloc logging
parent
dc88e6dd
Showing
- substrate/Cargo.lock 83 additions, 59 deletionssubstrate/Cargo.lock
- substrate/client/executor/src/wasm_runtime.rs 1 addition, 1 deletionsubstrate/client/executor/src/wasm_runtime.rs
- substrate/client/executor/wasmtime/Cargo.toml 1 addition, 1 deletionsubstrate/client/executor/wasmtime/Cargo.toml
- substrate/client/executor/wasmtime/src/imports.rs 6 additions, 1 deletionsubstrate/client/executor/wasmtime/src/imports.rs
- substrate/client/executor/wasmtime/src/lib.rs 3 additions, 1 deletionsubstrate/client/executor/wasmtime/src/lib.rs
- substrate/client/executor/wasmtime/src/runtime.rs 46 additions, 10 deletionssubstrate/client/executor/wasmtime/src/runtime.rs
- substrate/client/tracing/src/logging/mod.rs 3 additions, 0 deletionssubstrate/client/tracing/src/logging/mod.rs
Please register or sign in to comment