sc-executor-wasmtime 0.20.0

Defines a `WasmRuntime` that uses the Wasmtime JIT to execute.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

[package]
name = "sc-executor-wasmtime"
version = "0.20.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
license = "GPL-3.0-or-later WITH Classpath-exception-2.0"
homepage = "https://substrate.io"
repository = "https://github.com/paritytech/substrate/"
description = "Defines a `WasmRuntime` that uses the Wasmtime JIT to execute."
readme = "README.md"

[package.metadata.docs.rs]
targets = ["x86_64-unknown-linux-gnu"]

[dependencies]
log = "0.4.17"
cfg-if = "1.0"
libc = "0.2.121"

# When bumping wasmtime do not forget to also bump rustix
# to exactly the same version as used by wasmtime!
wasmtime = { version = "6.0.0", default-features = false, features = [
	"cache",
	"cranelift",
	"jitdump",
	"parallel-compilation",
	"pooling-allocator"
] }
anyhow = "1.0.68"
sc-allocator = { version = "14.0.0" }
sc-executor-common = { version = "0.20.0" }
sp-runtime-interface = { version = "15.0.0" }
sp-wasm-interface = { version = "12.0.0", features = ["wasmtime"] }

# Here we include the rustix crate in the exactly same semver-compatible version as used by
# wasmtime and enable its 'use-libc' flag.
#
# By default rustix directly calls the appropriate syscalls completely bypassing libc;
# this doesn't have any actual benefits for us besides making it harder to debug memory
# problems (since then `mmap` etc. cannot be easily hooked into).
rustix = { version = "0.36.7", default-features = false, features = ["std", "mm", "fs", "param", "use-libc"] }
once_cell = "1.12.0"

[dev-dependencies]
wat = "1.0"
sc-runtime-test = { path = "../runtime-test" }
sp-io = { path = "../../../primitives/io" }
tempfile = "3.3.0"
paste = "1.0"
codec = { package = "parity-scale-codec", version = "3.2.2" }
cargo_metadata = "0.15.2"