github
/
cranelift
mirror of https://github.com/bytecodealliance/wasmtime.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6761 Commits
49 Branches
140 Tags
128 MiB
Tree: c420f65214
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c420f65214'
${ noResults }
cranelift/Cargo.lock

2862 lines
62 KiB
Raw Normal View History

Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
[[package]]
name = "addr2line"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.13.0"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "1b6a2d3371669ab3ca9797670853d61402b03d0b4b9ebf33d677dfa720203072"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
dependencies = [
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.22.0",
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
]
[[package]]
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
name = "adler"
version = "0.2.3"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "ee2a4ec343196209d6594e19543ae87a39f96d5534d7174822a3ad825dd6ed7e"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
Hook up all crates via path dependencies
5 years ago
[[package]]
name = "ahash"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f33b5018f120946c1dcf279194f238a9f146725593ead1c08fa47ff22b0b5d3"
dependencies = [
"const-random",
]
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
[[package]]
name = "ahash"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
version = "0.3.8"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
checksum = "e8fd72866655d1904d6b0997d0b07ba561047d070fbe29de039031c641b61217"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "aho-corasick"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.7.13"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "043164d8ba5c4c3035fec9bbee8647c0261d788f3474306f93bb65901cae0e86"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"memchr",
]
[[package]]
name = "ansi_term"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
dependencies = [
"winapi",
]
[[package]]
name = "anyhow"
externref: Address review feedback
4 years ago
version = "1.0.31"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "85bb70cc08ec97ca5450e6eba421deeea5f172c0fc61f78b5357b2a8e8be195f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "arbitrary"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.5"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "7cb544f1057eaaff4b34f8c4dcf56fc3cd04debd291998405d135017a7c3c0f4"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
dependencies = [
"derive_arbitrary",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "arrayref"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.3.6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "arrayvec"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cff77d8686867eceff3105329d4698d96c2391c176d5d03adc90c7389162b5b8"
[[package]]
name = "atty"
Bump version to 0.9.0 (#790)
5 years ago
version = "0.2.14"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Bump version to 0.9.0 (#790)
5 years ago
"hermit-abi",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"libc",
"winapi",
]
Hook up all crates via path dependencies
5 years ago
[[package]]
name = "autocfg"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
Bump version to 0.9.0 (#790)
5 years ago
[[package]]
name = "autocfg"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f8aac770f1885fd7e387acedd76065302551364496e46b3dd00860b2f8359b9d"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "backtrace"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.3.50"
externref: Address review feedback
4 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "46254cf2fdcdf1badb5934448c1bcbe046a56537b3987d96c51a7afc5d03f293"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
"addr2line",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cfg-if",
"libc",
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
"miniz_oxide",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"rustc-demangle",
]
[[package]]
name = "base64"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
[[package]]
name = "base64"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.12.3"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "3441f0f7b02788e948e47f457ca01f1d7e6d92c693bc132c22b087d3141c03ff"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "binaryen"
Update binaryen fuzzing dependency (#913) Fixes an infinite loop in fuzz test case generation, pulling in WebAssembly/binaryen#2637
5 years ago
version = "0.10.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update binaryen fuzzing dependency (#913) Fixes an infinite loop in fuzz test case generation, pulling in WebAssembly/binaryen#2637
5 years ago
checksum = "a51ad23b3c7ab468d9daa948201921879ef0052e561c250fd0b326e6f000f2dd"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"binaryen-sys",
]
[[package]]
name = "binaryen-sys"
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
version = "0.10.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
checksum = "df5829a7c89f7827e58866704e4dfdf48a635d73c6e5449c1a8a0ba5a319d28a"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cc",
"cmake",
"heck",
"regex",
]
[[package]]
name = "bincode"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.3.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "f30d3a39baa26f9651f17b375061f3233dde33424a8b72b0dbe93a68a0bc896d"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"byteorder",
"serde",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "bit-set"
externref: Address review feedback
4 years ago
version = "0.5.2"
Fix wiggle's tests
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "6e11e16035ea35e4e5997b393eacbf6f63983188f7a2ad25bfb13465f5ad59de"
Fix wiggle's tests
5 years ago
dependencies = [
"bit-vec",
]
[[package]]
name = "bit-vec"
externref: Address review feedback
4 years ago
version = "0.6.2"
Fix wiggle's tests
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "5f0dc55f2d8a1a85650ac47858bb001b4c0dd73d79e3c455a842925e68d29cd3"
Fix wiggle's tests
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "bitflags"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
[[package]]
name = "blake2b_simd"
Bump version to 0.9.0 (#790)
5 years ago
version = "0.5.10"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "d8fb2d74254a3a0b5cac33ac9f8ed0e44aa50378d9dbb2e5d83bd21ed1dc2c8a"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"arrayref",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"arrayvec",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"constant_time_eq",
]
[[package]]
name = "block-buffer"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0940dc441f31689269e10ac70eb1002a3a1d3ad1390e030043662eb7fe4688b"
dependencies = [
"block-padding",
"byte-tools",
"byteorder",
"generic-array",
]
[[package]]
name = "block-padding"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa79dedbb091f449f1f39e53edf88d5dbe95f895dae6135a8d7b881fb5af73f5"
dependencies = [
"byte-tools",
]
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
[[package]]
name = "bumpalo"
externref: Address review feedback
4 years ago
version = "3.4.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "2e8c087f005730276d1096a652e92a8bacee2e2472bcc9715a74d2bec38b5820"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "byte-tools"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7"
[[package]]
name = "byteorder"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
version = "1.3.4"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
checksum = "08c48aae112d48ed9f069b33538ea9e3e90aa263cfa3d1c24309612b1f7472de"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "capstone"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "031ba51c39151a1d6336ec859646153187204b0147c7b3f6fe2de636f1b8dbb3"
dependencies = [
"capstone-sys",
]
[[package]]
name = "capstone-sys"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fae25eddcb80e24f98c35952c37a91ff7f8d0f60dbbdafb9763e8d5cc566b8d7"
dependencies = [
"cc",
]
[[package]]
name = "cc"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.58"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "f9a06fb2e53271d7c279ec1efea6ab691c35a2ae67ec0d91d7acec0caf13b518"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"jobserver",
]
[[package]]
name = "cfg-if"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "chrono"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.13"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "c74d84029116787153e02106bf53e66828452a4b325cc8652b788b5967c0a0b6"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"num-integer",
"num-traits",
"time",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "clap"
externref: Address review feedback
4 years ago
version = "2.33.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "bdfa80d47f954d53a35a64987ca1422f495b8d6483c0fe9f7117b36c2a792129"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"ansi_term",
"atty",
"bitflags",
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
"strsim",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"textwrap",
"unicode-width",
"vec_map",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
dependencies = [
"bitflags",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cmake"
externref: Address review feedback
4 years ago
version = "0.1.44"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "0e56268c17a6248366d66d4a47a3381369d068cce8409bb1716ed77ea32163bb"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cc",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "console"
externref: Address review feedback
4 years ago
version = "0.11.3"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "8c0994e656bba7b922d8dd1245db90672ffb701e684e45be58f20719d69abc5a"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"encode_unicode",
"lazy_static",
"libc",
"regex",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"terminal_size",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"termios",
"unicode-width",
"winapi",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"winapi-util",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
]
Hook up all crates via path dependencies
5 years ago
[[package]]
name = "const-random"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2f1af9ac737b2dd2d577701e59fd09ba34822f6f2ebdb30a7647405d9e55e16a"
dependencies = [
"const-random-macro",
"proc-macro-hack",
]
[[package]]
name = "const-random-macro"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "25e4c606eb459dd29f7c57b2e0879f2b6f14ee130918c2b78ccb58a9624e6c7a"
dependencies = [
"getrandom",
"proc-macro-hack",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "constant_time_eq"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.1.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "245097e9a4535ee1e3e3931fcfcd55a796a44c643e8596ff6566d68f09b87bbc"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cpu-time"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e9e393a7668fe1fad3075085b86c781883000b4ede868f43627b34a87c8b7ded"
dependencies = [
"libc",
"winapi",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "cranelift"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"cranelift-codegen",
"cranelift-frontend",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cranelift-bforest"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cranelift-entity",
]
[[package]]
name = "cranelift-codegen"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
mach backend: allow snapshotting IR graphs with the SNAPSHOT_REGALLOC env variable; This also requires the serde feature, which isn't enabled by default, thus it must be passed as a command-line argument to cargo.
4 years ago
"bincode",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"byteorder",
"cranelift-bforest",
"cranelift-codegen-meta",
"cranelift-codegen-shared",
"cranelift-entity",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.21.0",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"hashbrown 0.7.2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"peepmatic",
"peepmatic-runtime",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"peepmatic-traits",
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
"regalloc",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"serde",
"smallvec",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"wast 15.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "cranelift-codegen-meta"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cranelift-codegen-shared",
"cranelift-entity",
]
[[package]]
name = "cranelift-codegen-shared"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cranelift-entity"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"serde",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "cranelift-faerie"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"anyhow",
"cranelift-codegen",
"cranelift-module",
wasmtime-cli, obj, debug: upgrade to faerie 0.15 eliminating the faerie 0.14 dep
5 years ago
"faerie",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"goblin",
"target-lexicon",
]
[[package]]
name = "cranelift-filetests"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"byteorder",
"cranelift-codegen",
Add ability to call CLIF functions with arbitrary arguments in filetests This resolves the work started in https://github.com/bytecodealliance/cranelift/pull/1231 and https://github.com/bytecodealliance/wasmtime/pull/1436. Cranelift filetests currently have the ability to run CLIF functions with a signature like `() -> b*` and check that the result is true under the `test run` directive. This PR adds the ability to call functions with arbitrary arguments and non-boolean returns and either print the result or check against a list of expected results: - `run` commands look like `; run: %add(2, 2) == 4` or `; run: %add(2, 2) != 5` and verify that the executed CLIF function returns the expected value - `print` commands look like `; print: %add(2, 2)` and print the result of the function to stdout To make this work, this PR compiles a single Cranelift `Function` into a `CompiledFunction` using a `SingleFunctionCompiler`. Because we will not know the signature of the function until runtime, we use a `Trampoline` to place the values in the appropriate location for the calling convention; this should look a lot like what @alexcrichton is doing with `VMTrampoline` in wasmtime (see https://github.com/bytecodealliance/wasmtime/blob/3b7cb6ee64469470fcdd68e185abca8eb2a1b20a/crates/api/src/func.rs#L510-L526, https://github.com/bytecodealliance/wasmtime/blob/3b7cb6ee64469470fcdd68e185abca8eb2a1b20a/crates/jit/src/compiler.rs#L260). To avoid re-compiling `Trampoline`s for the same function signatures, `Trampoline`s are cached in the `SingleFunctionCompiler`.
5 years ago
"cranelift-frontend",
Add `test interpret` support to filetests
5 years ago
"cranelift-interpreter",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"cranelift-native",
"cranelift-preopt",
"cranelift-reader",
"file-per-thread-logger",
"filecheck",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.21.0",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"log",
"memmap",
"num_cpus",
ARM64 backend, part 10 / 11: filetest support for VCode tests. This patch adds support for filetests with the `vcode` type. This allows test cases to feed CLIF into the new backend, produce VCode output with machine instructions, and then perform matching against the pretty-printed text representation of the VCode. Tests for the new ARM64 backend using this infrastructure will come in a followup patch.
5 years ago
"target-lexicon",
Add ability to call CLIF functions with arbitrary arguments in filetests This resolves the work started in https://github.com/bytecodealliance/cranelift/pull/1231 and https://github.com/bytecodealliance/wasmtime/pull/1436. Cranelift filetests currently have the ability to run CLIF functions with a signature like `() -> b*` and check that the result is true under the `test run` directive. This PR adds the ability to call functions with arbitrary arguments and non-boolean returns and either print the result or check against a list of expected results: - `run` commands look like `; run: %add(2, 2) == 4` or `; run: %add(2, 2) != 5` and verify that the executed CLIF function returns the expected value - `print` commands look like `; print: %add(2, 2)` and print the result of the function to stdout To make this work, this PR compiles a single Cranelift `Function` into a `CompiledFunction` using a `SingleFunctionCompiler`. Because we will not know the signature of the function until runtime, we use a `Trampoline` to place the values in the appropriate location for the calling convention; this should look a lot like what @alexcrichton is doing with `VMTrampoline` in wasmtime (see https://github.com/bytecodealliance/wasmtime/blob/3b7cb6ee64469470fcdd68e185abca8eb2a1b20a/crates/api/src/func.rs#L510-L526, https://github.com/bytecodealliance/wasmtime/blob/3b7cb6ee64469470fcdd68e185abca8eb2a1b20a/crates/jit/src/compiler.rs#L260). To avoid re-compiling `Trampoline`s for the same function signatures, `Trampoline`s are cached in the `SingleFunctionCompiler`.
5 years ago
"thiserror",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cranelift-frontend"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cranelift-codegen",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"hashbrown 0.7.2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
"smallvec",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Add `test interpret` support to filetests
5 years ago
[[package]]
name = "cranelift-interpreter"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Add `test interpret` support to filetests
5 years ago
dependencies = [
"cranelift-codegen",
"cranelift-entity",
"cranelift-frontend",
"cranelift-reader",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"hashbrown 0.7.2",
Add `test interpret` support to filetests
5 years ago
"log",
"thiserror",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "cranelift-module"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
cranelift-faerie: upgrade to faerie 0.15.0, fix error reporting the `FaerieProduct` exposes faerie-specific types, so we can give the `faerie::ArtifactError` on those methods. `ModuleError::Backend` now expects an `anyhow::Error`, so we change a .to_string into .into() and retain better error information.
5 years ago
"anyhow",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"cranelift-codegen",
"cranelift-entity",
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"hashbrown 0.6.3",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"log",
"thiserror",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cranelift-native"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cranelift-codegen",
"raw-cpuid",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "cranelift-object"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
Bump object to 0.19.0 (#1767) * Bump object to 0.19.0
4 years ago
"anyhow",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"cranelift-codegen",
"cranelift-module",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"target-lexicon",
]
[[package]]
name = "cranelift-preopt"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"cranelift-codegen",
"cranelift-entity",
]
Merge cranelift/wasmtime fuzzing
5 years ago
[[package]]
name = "cranelift-reader"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Merge cranelift/wasmtime fuzzing
5 years ago
dependencies = [
"cranelift-codegen",
cranelift/reader/src/parser.rs: fn parse_inst_resuts: produce the results as a SmallVec<[Value; 1]>, not as a Vec<Value>. This isn't a useful change for any non-developer use of Cranelift, but it does significantly reduce the amount of allocation "noise" seen when tuning the new backend pipeline as driven by clif-util reading .clif files. In one case the number of malloc calls declined by about 20% with this change.
5 years ago
"smallvec",
Merge cranelift/wasmtime fuzzing
5 years ago
"target-lexicon",
Cast DataValues to and from native types Also, returns a `Result` in the `RunCommand::run` helper.
5 years ago
"thiserror",
Merge cranelift/wasmtime fuzzing
5 years ago
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "cranelift-serde"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"clap",
"cranelift-codegen",
"cranelift-reader",
"serde",
"serde_derive",
"serde_json",
]
[[package]]
name = "cranelift-simplejit"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"cranelift",
"cranelift-codegen",
"cranelift-entity",
"cranelift-frontend",
"cranelift-module",
"cranelift-native",
"errno",
"libc",
"memmap",
"region",
"target-lexicon",
"winapi",
]
[[package]]
name = "cranelift-tools"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"capstone",
"cfg-if",
"clap",
"cranelift",
"cranelift-codegen",
"cranelift-entity",
"cranelift-faerie",
"cranelift-filetests",
"cranelift-frontend",
Add an `interpret` command to clif-util
5 years ago
"cranelift-interpreter",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"cranelift-module",
"cranelift-native",
"cranelift-object",
"cranelift-preopt",
"cranelift-reader",
"cranelift-serde",
"cranelift-simplejit",
"cranelift-wasm",
"file-per-thread-logger",
"filecheck",
"indicatif",
Add an `interpret` command to clif-util
5 years ago
"log",
bump witx dep to 0.8.5
5 years ago
"pretty_env_logger",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"target-lexicon",
"term",
Add an `interpret` command to clif-util
5 years ago
"thiserror",
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"walkdir",
"wat",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "cranelift-wasm"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cranelift-codegen",
"cranelift-entity",
"cranelift-frontend",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"hashbrown 0.7.2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
"serde",
Hook up all crates via path dependencies
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Hook up all crates via path dependencies
5 years ago
"wat",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
[[package]]
name = "crc32fast"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ba125de2af0df55319f41944744ad91c71113bf74a4646efff39afe1f6842db1"
dependencies = [
"cfg-if",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "crossbeam-deque"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
version = "0.7.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
checksum = "9f02af974daeee82218205558e51ec8768b48cf524bd01d550abe5573a608285"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"crossbeam-epoch",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"crossbeam-utils",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"maybe-uninit",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "crossbeam-epoch"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
version = "0.8.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
checksum = "058ed274caafc1f60c4997b5fc07bf7dc7cca454af7c6e81edffe5f33f70dace"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Hook up all crates via path dependencies
5 years ago
"autocfg 1.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cfg-if",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"crossbeam-utils",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"lazy_static",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"maybe-uninit",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"memoffset",
"scopeguard",
]
[[package]]
name = "crossbeam-queue"
externref: Address review feedback
4 years ago
version = "0.2.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "774ba60a54c213d409d5353bda12d49cd68d14e45036a285234c8d6f91f92570"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Bump version to 0.9.0 (#790)
5 years ago
"cfg-if",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"crossbeam-utils",
externref: Address review feedback
4 years ago
"maybe-uninit",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "crossbeam-utils"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
version = "0.7.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
checksum = "c3c7c73a2d1e9fc0886a08b93e98eb643461230d5f1925e4036204d5f2e261a8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Hook up all crates via path dependencies
5 years ago
"autocfg 1.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cfg-if",
"lazy_static",
]
[[package]]
name = "cvt"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34ac344c7efccb80cd25bc61b2170aec26f2f693fd40e765a539a1243db48c71"
dependencies = [
"cfg-if",
]
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
[[package]]
name = "derive_arbitrary"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.5"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "02b43185d3e7ce7dcd44a23ca761ec026359753ebf480283a571e6463853d2ef"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
"quote",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"syn",
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
]
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
[[package]]
name = "derive_more"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.99.9"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "298998b1cf6b5b2c8a7b023dfd45821825ce3ba8a8af55c921a0e734e4653f76"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "derive_utils"
externref: Address review feedback
4 years ago
version = "0.10.0"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "3df5480412da86cdf5d6b7f3b682422c84359ff7399aa658df1d15ee83244b1d"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Upgrade to witx 0.8.0 with tagged unions (#921) * witx tagged unions: updates to wig to use new semantics * wig: emit a `#variant: ()` union variant for empty variants * wasi-common: translate to use tagged unions * update to flattened layout of event struct * wig: generate layout tests, and delete bindgen ones the bindgen tests became out-of-date with the latest changes to the representation of unions, and the re-jiggering of various struct definitions that went along with it. * wasi: point at master with tagged union PR merged * fix event struct repr on windows
5 years ago
[[package]]
name = "diff"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0e25ea47919b1560c4e3b7fe0aaab9becf5b84a10325ddf7db0f0ba5e1026499"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "digest"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f3d0c8c8752312f9713efd397ff63acb9f85585afbf179282e720e7704954dd5"
dependencies = [
"generic-array",
]
[[package]]
name = "directories"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "551a778172a450d7fc12e629ca3b0428d00f6afa9a43da1b630d54604e97371c"
dependencies = [
"cfg-if",
"dirs-sys",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "dirs"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
dependencies = [
"cfg-if",
"dirs-sys",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "dirs-sys"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
version = "0.3.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
checksum = "8e93d7f5705de3e49895a2b5e0b8855a1c27f080192ae9c32a6432d50741a57a"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
"redox_users",
"winapi",
]
[[package]]
name = "dynasm"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "42a814e1edeb85dd2a3c6fc0d6bf76d02ca5695d438c70ecee3d90774f3259c5"
dependencies = [
"bitflags",
"byteorder",
"lazy_static",
"owning_ref",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "dynasmrt"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a393aaeb4441a48bcf47b5b6155971f82cc1eb77e22855403ccc0415ac8328d"
dependencies = [
"byteorder",
"memmap",
]
[[package]]
name = "either"
version = "1.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bb1f6b1ce1c140482ea30ddd3335fc0024ac7ee112895426e0a629a6c20adfe3"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "encode_unicode"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "env_logger"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44533bbbb3bb3c1fa17d9f2e4e38bbbaf8396ba82193c4cb1b6445d711445d36"
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
[[package]]
name = "errno"
Fixes for 0.15 (#1449) * Wasmtime 0.15.0 and Cranelift 0.62.0. (#1398) * Bump more ad-hoc versions. * Add build.rs to wasi-common's Cargo.toml. * Update the env var name in more places. * Remove a redundant echo.
5 years ago
version = "0.2.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Fixes for 0.15 (#1449) * Wasmtime 0.15.0 and Cranelift 0.62.0. (#1398) * Bump more ad-hoc versions. * Add build.rs to wasi-common's Cargo.toml. * Update the env var name in more places. * Remove a redundant echo.
5 years ago
checksum = "b480f641ccf0faf324e20c1d3e53d81b7484c698b42ea677f6907ae4db195371"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"errno-dragonfly",
"libc",
"winapi",
]
[[package]]
name = "errno-dragonfly"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14ca354e36190500e1e1fb267c647932382b54053c50b14970856c0b00a35067"
dependencies = [
"gcc",
"libc",
]
Move all examples to a top-level directory (#1286) * Move all examples to a top-level directory This commit moves all API examples (Rust and C) to a top-level `examples` directory. This is intended to make it more discoverable and conventional as to where examples are located. Additionally all examples are now available in both Rust and C to see how to execute the example in the language you're familiar with. The intention is that as more languages are supported we'd add more languages as examples here too. Each example is also accompanied by either a `*.wat` file which is parsed as input, or a Rust project in a `wasm` folder which is compiled as input. A simple driver crate was also added to `crates/misc` which executes all the examples on CI, ensuring the C and Rust examples all execute successfully.
5 years ago
[[package]]
name = "example-fib-debug-wasm"
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
version = "0.0.0"
Move all examples to a top-level directory (#1286) * Move all examples to a top-level directory This commit moves all API examples (Rust and C) to a top-level `examples` directory. This is intended to make it more discoverable and conventional as to where examples are located. Additionally all examples are now available in both Rust and C to see how to execute the example in the language you're familiar with. The intention is that as more languages are supported we'd add more languages as examples here too. Each example is also accompanied by either a `*.wat` file which is parsed as input, or a Rust project in a `wasm` folder which is compiled as input. A simple driver crate was also added to `crates/misc` which executes all the examples on CI, ensuring the C and Rust examples all execute successfully.
5 years ago
Add examples of linking and WASI (#1369) * Add examples of linking and WASI This commit adds two example programs, one for linking two modules together and one for instantiating WASI. The linkage example additionally uses WASI to get some meaningful output at this time. cc #1272 * Add examples to the book as well * More links! * Ignore examples from rustdoc testsing * More example updates * More ignored
5 years ago
[[package]]
name = "example-wasi-wasm"
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
version = "0.0.0"
Add examples of linking and WASI (#1369) * Add examples of linking and WASI This commit adds two example programs, one for linking two modules together and one for instantiating WASI. The linkage example additionally uses WASI to get some meaningful output at this time. cc #1272 * Add examples to the book as well * More links! * Ignore examples from rustdoc testsing * More example updates * More ignored
5 years ago
cranelift-faerie: upgrade to faerie 0.15.0, fix error reporting the `FaerieProduct` exposes faerie-specific types, so we can give the `faerie::ArtifactError` on those methods. `ModuleError::Backend` now expects an `anyhow::Error`, so we change a .to_string into .into() and retain better error information.
5 years ago
[[package]]
name = "faerie"
version = "0.15.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dfef65b0e94693295c5d2fe2506f0ee6f43465342d4b5331659936aee8b16084"
dependencies = [
"goblin",
"indexmap",
"log",
"scroll",
"string-interner",
"target-lexicon",
"thiserror",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "fake-simd"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e88a8acf291dafb59c2d96e8f59828f3838bb1a70398823ade51a84de6a6deed"
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
[[package]]
name = "file-per-thread-logger"
externref: Address review feedback
4 years ago
version = "0.1.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "8b3937f028664bd0e13df401ba49a4567ccda587420365823242977f06609ed1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
externref: Address review feedback
4 years ago
"env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
]
Test basic DWARF generation (#931) * Add obj generation with debug info * Add simple transform check
5 years ago
[[package]]
name = "filecheck"
Update the `filecheck` dependency (#1348) Removes an edge towards the `synstructure` dependency in our dependency graph which, if removed entirely, is hoped to reduce build times locally and on CI as you switch between `cargo build` and `cargo test` because deep dependencies like `syn` won't have their features alternating back and forth.
5 years ago
version = "0.5.0"
Test basic DWARF generation (#931) * Add obj generation with debug info * Add simple transform check
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update the `filecheck` dependency (#1348) Removes an edge towards the `synstructure` dependency in our dependency graph which, if removed entirely, is hoped to reduce build times locally and on CI as you switch between `cargo build` and `cargo test` because deep dependencies like `syn` won't have their features alternating back and forth.
5 years ago
checksum = "2fe00b427b7c4835f8b82170eb7b9a63634376b63d73b9a9093367e82570bbaa"
Test basic DWARF generation (#931) * Add obj generation with debug info * Add simple transform check
5 years ago
dependencies = [
"regex",
Update the `filecheck` dependency (#1348) Removes an edge towards the `synstructure` dependency in our dependency graph which, if removed entirely, is hoped to reduce build times locally and on CI as you switch between `cargo build` and `cargo test` because deep dependencies like `syn` won't have their features alternating back and forth.
5 years ago
"thiserror",
Test basic DWARF generation (#931) * Add obj generation with debug info * Add simple transform check
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "filetime"
externref: Address review feedback
4 years ago
version = "0.2.10"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "affc17579b132fc2461adf7c575cc6e8b134ebca52c51f5411388965227dc695"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cfg-if",
"libc",
"redox_syscall",
"winapi",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "fnv"
externref: Address review feedback
4 years ago
version = "1.0.7"
Fix wiggle's tests
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Fix wiggle's tests
5 years ago
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
[[package]]
name = "fst"
externref: Address review feedback
4 years ago
version = "0.4.4"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "a7293de202dbfe786c0b3fe6110a027836c5438ed06db7b715c9955ff4bfea51"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
Fix wiggle's tests
5 years ago
[[package]]
name = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "gcc"
version = "0.3.55"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f5f3913fa0bfe7ee1fd8248b6b9f42a5af4b9d65ec2dd2c3c26132b950ecfc2"
[[package]]
name = "generic-array"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c68f0274ae0e023facc3c97b2e00f076be70e254bc851d972503b328db79b2ec"
dependencies = [
"typenum",
]
[[package]]
name = "getrandom"
Bump version to 0.9.0 (#790)
5 years ago
version = "0.1.14"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "7abc8dd8451921606d809ba32e95b6111925cd2906060d2dcc29c070220503eb"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cfg-if",
"libc",
"wasi",
]
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
[[package]]
name = "gimli"
Upgrade gimli to 0.21 (#1819) * Use gimli 0.21 * rm CFI w Expression * Don't write .debug_frame twice
4 years ago
version = "0.21.0"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade gimli to 0.21 (#1819) * Use gimli 0.21 * rm CFI w Expression * Don't write .debug_frame twice
4 years ago
checksum = "bcc8e0c9bce37868955864dbecd2b1ab2bdf967e6f28066d65aaac620444b65c"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"fallible-iterator",
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
"indexmap",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"stable_deref_trait",
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
]
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
[[package]]
name = "gimli"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aaf91faf136cb47367fa430cd46e37a788775e7fa104f8b4bcb3861dc389b724"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
[[package]]
name = "goblin"
Bump version to 0.9.0 (#790)
5 years ago
version = "0.1.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "3081214398d39e4bd7f2c1975f0488ed04614ffdd976c6fc7a0708278552c0da"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"log",
"plain",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"scroll",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Hook up all crates via path dependencies
5 years ago
[[package]]
name = "hashbrown"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8e6073d0ca812575946eb5f35ff68dbe519907b25c42530389ff946dc84c6ead"
dependencies = [
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"ahash 0.2.18",
Hook up all crates via path dependencies
5 years ago
"autocfg 0.1.7",
]
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
[[package]]
name = "hashbrown"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
version = "0.7.2"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
checksum = "96282e96bfcd3da0d3aa9938bedf1e50df3269b6db08b4876d2da0bb1a0841cf"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
dependencies = [
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
"ahash 0.3.8",
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"autocfg 1.0.0",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "heck"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
dependencies = [
"unicode-segmentation",
]
[[package]]
name = "hermit-abi"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.15"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "3deed196b6e7f9e44a2ae8d94225d80302d81208b1bb673fd21fe634645c85a9"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
]
[[package]]
name = "humantime"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
dependencies = [
"quick-error",
]
[[package]]
name = "indexmap"
externref: Address review feedback
4 years ago
version = "1.4.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "c398b2b113b55809ceb9ee3e753fcbac793f1956663f3c36549c1346015c2afe"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Hook up all crates via path dependencies
5 years ago
"autocfg 1.0.0",
Make wasmtime_environ::Module serializable (#2005) * Define WasmType/WasmFuncType in the Cranelift * Make `Module` serializable
4 years ago
"serde",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "indicatif"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8572bccfb0665e70b7faf44ee28841b8e0823450cd4ad562a76b5a3c4bf48487"
dependencies = [
"console",
"lazy_static",
"number_prefix",
"regex",
]
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
[[package]]
name = "iter-enum"
externref: Address review feedback
4 years ago
version = "0.2.4"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "2cdea9771bec3d95893f6c665a4fcd477af7858446a46bc2772f560534eee43b"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
dependencies = [
"derive_utils",
"quote",
"syn",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "itertools"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f56a2d0bc861f9165be4eb3442afd3c236d8a98afd426f65d92324ae1091a484"
dependencies = [
"either",
]
externref: Address review feedback
4 years ago
[[package]]
name = "itertools"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "284f18f85651fe11e8a991b2adb42cb078325c996ed026d994719efcfca1d54b"
dependencies = [
"either",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "itoa"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "dc6f3ad7b9d11a0c00842ff8de1b60ee58661048eb8049ed33c73594f359d7e6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Adds JIT profiling support for VTune (#819) This patch adds initial support for ittapi which is an open source profiling api for instrumentation and tracing and profiling of jitted code. Result files can be read by VTune for analysis Build: cargo build --features=vtune Profile: // Using amplxe-cl from VTune amplxe-cl -v -collect hostpost target/debug/wasmtime --vtune test.wasm
5 years ago
[[package]]
name = "ittapi-rs"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa16daf7106319e5c4456733e33aeb64d8c986af0127bc25eb6d9e84e2f1f8b0"
dependencies = [
"cmake",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "jobserver"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
version = "0.1.21"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
checksum = "5c71313ebb9439f74b00d9d2dcec36440beaf57a6aa0623068441dd7cd81a7f2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
]
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
[[package]]
name = "leb128"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3576a87f2ba00f6f106fdfcd16db1d698d648a26ad8e0573cad8537c3c362d2a"
[[package]]
name = "libc"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.2.72"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "a9f8082297d534141b30c8d39e9b1773713ab50fdbe4ff30f750d063b3bfd701"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
[[package]]
name = "libfuzzer-sys"
Update `arbitrary` and `libfuzzer` dependencies
5 years ago
version = "0.3.2"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `arbitrary` and `libfuzzer` dependencies
5 years ago
checksum = "8d718794b8e23533b9069bd2c4597d69e41cc7ab1c02700a502971aca0cdcf24"
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
dependencies = [
Update to arbitrary@0.4.0 and libfuzzer-sys@0.3.1
5 years ago
"arbitrary",
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
"cc",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "lightbeam"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
"capstone",
"cranelift-codegen",
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
"derive_more",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"dynasm",
"dynasmrt",
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
"iter-enum",
externref: Address review feedback
4 years ago
"itertools 0.8.2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"lazy_static",
"memoffset",
"more-asserts",
"quickcheck",
"smallvec",
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
"staticvec",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
"typemap",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wat",
]
[[package]]
name = "log"
version = "0.4.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14b6052be84e6b71ab17edffc2eeabf5c2c3ae1fdb464aae35ac50c67a44e1f7"
dependencies = [
"cfg-if",
]
[[package]]
name = "mach"
externref: Address review feedback
4 years ago
version = "0.3.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "b823e83b2affd8f40a9ee8c29dbc56404c1e34cd2710921f2801e2cf29527afa"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
]
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "matchers"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f099785f7595cc4b4553a174ce30dd7589ef93391ff414dbb67f62392b9e0ce1"
dependencies = [
"regex-automata",
]
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
[[package]]
name = "maybe-uninit"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60302e4db3a61da70c0cb7991976248362f30319e88850c487b9b95bbf059e00"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "memchr"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
version = "2.3.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
checksum = "3728d817d99e5ac407411fa471ff9800a778d88a24685968b36824eaf4bee400"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "memmap"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6585fd95e7bb50d6cc31e20d4cf9afb4e2ba16c5846fc76793f11218da9c475b"
dependencies = [
"libc",
"winapi",
]
[[package]]
name = "memoffset"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.5.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "c198b026e1bbf08a937e94c6c60f9ec4a2267f5b0d2eec9c1b21b061ce2be55f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"autocfg 1.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
[[package]]
name = "miniz_oxide"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.0"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "be0f75932c1f6cfae3c04000e40114adf955636e19040f9c0a2c380702aa1c7f"
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
dependencies = [
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"adler",
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "more-asserts"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0debeb9fcf88823ea64d64e4a815ab1643f33127d995978e099942ce38f25238"
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "num-integer"
externref: Address review feedback
4 years ago
version = "0.1.43"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "8d59457e662d541ba17869cf51cf177c0b5f0cbf476c66bdc90bf1edac4f875b"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"autocfg 1.0.0",
"num-traits",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "num-traits"
externref: Address review feedback
4 years ago
version = "0.2.12"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "ac267bcc07f48ee5f8935ab0d24f316fb722d7a1292e2913f0cc196b29ffd611"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Hook up all crates via path dependencies
5 years ago
"autocfg 1.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "num_cpus"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
version = "1.13.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"hermit-abi",
"libc",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "number_prefix"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17b02fc0ff9a9e4b35b3342880f48e896ebf69f2967921fe8646bf5b7125956a"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
[[package]]
name = "object"
version = "0.19.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9cbca9424c482ee628fa549d9c812e2cd22f1180b9222c9200fdfa6eb31aecb2"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
[[package]]
name = "object"
Update various crates' `object` and `wast` dependencies (#1908) This somewhat cuts down on duplicate dependencies. `wast` is used in a much older version (`11.0.0`) by `witx`, and can be updated without issues there as well, but this at least gets us from 3 copies to 2.
4 years ago
version = "0.20.0"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update various crates' `object` and `wast` dependencies (#1908) This somewhat cuts down on duplicate dependencies. `wast` is used in a much older version (`11.0.0`) by `witx`, and can be updated without issues there as well, but this at least gets us from 3 copies to 2.
4 years ago
checksum = "1ab52be62400ca80aa00285d25253d7f7c437b7375c4de678f5405d3afe82ca5"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
dependencies = [
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
"crc32fast",
"indexmap",
Write ELF image and instantiate code_memory from it (#1931) - Create the ELF image from Compilation - Create CodeMemory from the ELF image - Link using ELF image - Remove creation of GDB JIT images from crates/debug - Move make_trampoline from compiler.rs
4 years ago
"wasmparser 0.57.0",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
]
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
[[package]]
name = "once_cell"
externref: Address review feedback
4 years ago
version = "1.4.0"
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "0b631f7e854af39a1739f401cf34a8a013dfe09eac4fa4dba91e9768bd28168d"
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "opaque-debug"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2839e79665f131bdb5782e51f2c6c9599c133c6098982a54c794358bf432529c"
[[package]]
name = "os_pipe"
externref: Address review feedback
4 years ago
version = "0.9.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "fb233f06c2307e1f5ce2ecad9f8121cffbbee2c95428f44ea85222e460d0d213"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
"winapi",
]
[[package]]
name = "owning_ref"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
version = "0.4.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
checksum = "6ff55baddef9e4ad00f88b6c743a2a8062d4c6ade126c2a528644b8e444d52ce"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"stable_deref_trait",
]
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
[[package]]
name = "peepmatic"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.66.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"anyhow",
"peepmatic-automata",
"peepmatic-macro",
"peepmatic-runtime",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"peepmatic-test-operator",
"peepmatic-traits",
"serde",
deps: Update `wast` to 15.0.0 This also updates `wat` in the lockfile so that the SIMD spec tests are passing again.
5 years ago
"wast 15.0.0",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"z3",
]
[[package]]
name = "peepmatic-automata"
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
version = "0.66.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"serde",
]
[[package]]
name = "peepmatic-fuzzing"
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
version = "0.66.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"arbitrary",
"bincode",
externref: Address review feedback
4 years ago
"env_logger",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"fst",
"log",
"peepmatic",
"peepmatic-automata",
"peepmatic-runtime",
"peepmatic-test",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"peepmatic-test-operator",
"peepmatic-traits",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"rand 0.7.3",
"serde",
deps: Update `wast` to 15.0.0 This also updates `wat` in the lockfile so that the SIMD spec tests are passing again.
5 years ago
"wast 15.0.0",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
]
[[package]]
name = "peepmatic-macro"
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
version = "0.66.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "peepmatic-runtime"
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
version = "0.66.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"bincode",
"bumpalo",
"log",
"peepmatic-automata",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"peepmatic-test-operator",
"peepmatic-traits",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"serde",
Implement customer [de]serialization for `IntegerInterner` Added some basic tests that the representation of the interner is only the `values` sequence, and that it round-trips successfully.
4 years ago
"serde_test",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"thiserror",
deps: Update `wast` to 15.0.0 This also updates `wat` in the lockfile so that the SIMD spec tests are passing again.
5 years ago
"wast 15.0.0",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
]
[[package]]
name = "peepmatic-test"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
version = "0.2.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
externref: Address review feedback
4 years ago
"env_logger",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"log",
"peepmatic",
"peepmatic-runtime",
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
"peepmatic-test-operator",
"peepmatic-traits",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
]
peepmatic: Be generic over the operator type This lets us avoid the cost of `cranelift_codegen::ir::Opcode` to `peepmatic_runtime::Operator` conversion overhead, and paves the way for allowing Peepmatic to support non-clif optimizations (e.g. vcode optimizations). Rather than defining our own `peepmatic::Operator` type like we used to, now the whole `peepmatic` crate is effectively generic over a `TOperator` type parameter. For the Cranelift integration, we use `cranelift_codegen::ir::Opcode` as the concrete type for our `TOperator` type parameter. For testing, we also define a `TestOperator` type, so that we can test Peepmatic code without building all of Cranelift, and we can keep them somewhat isolated from each other. The methods that `peepmatic::Operator` had are now translated into trait bounds on the `TOperator` type. These traits need to be shared between all of `peepmatic`, `peepmatic-runtime`, and `cranelift-codegen`'s Peepmatic integration. Therefore, these new traits live in a new crate: `peepmatic-traits`. This crate acts as a header file of sorts for shared trait/type/macro definitions. Additionally, the `peepmatic-runtime` crate no longer depends on the `peepmatic-macro` procedural macro crate, which should lead to faster build times for Cranelift when it is using pre-built peephole optimizers.
4 years ago
[[package]]
name = "peepmatic-test-operator"
version = "0.66.0"
dependencies = [
"peepmatic-traits",
"serde",
"wast 15.0.0",
]
[[package]]
name = "peepmatic-traits"
version = "0.66.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "plain"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4596b6d070b27117e987119b4dac604f3c58cfb0b191112e24771b2faeac1a6"
[[package]]
name = "ppv-lite86"
externref: Address review feedback
4 years ago
version = "0.2.8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "237a5ed80e274dbc66f86bd59c1e25edc039660be53194b5fe0a482e0f2612ea"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
[[package]]
name = "pretty_env_logger"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "926d36b9553851b8b0005f1275891b392ee4d2d833852c417ed025477350fb9d"
dependencies = [
externref: Address review feedback
4 years ago
"env_logger",
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"log",
]
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
[[package]]
name = "proc-macro-error"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.3"
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "fc175e9777c3116627248584e8f8b3e2987405cabe1c0adf7d1dd28f09dc7880"
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
dependencies = [
Bump version to 0.9.0 (#790)
5 years ago
"proc-macro-error-attr",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
"version_check",
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
]
Bump version to 0.9.0 (#790)
5 years ago
[[package]]
name = "proc-macro-error-attr"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.3"
Bump version to 0.9.0 (#790)
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "3cc9795ca17eb581285ec44936da7fc2335a3f34f2ddd13118b6f4d515435c50"
Bump version to 0.9.0 (#790)
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Bump version to 0.9.0 (#790)
5 years ago
"syn-mid",
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
"version_check",
Bump version to 0.9.0 (#790)
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "proc-macro-hack"
externref: Address review feedback
4 years ago
version = "0.5.16"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "7e0456befd48169b9f13ef0f0ad46d492cf9d2dbb918bcf38e01eed4ce3ec5e4"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "proc-macro2"
externref: Address review feedback
4 years ago
version = "1.0.18"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "beae6331a816b1f65d04c45b078fd8e6c93e8071771f41b8163255bbd8d7c8fa"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"unicode-xid",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Fix wiggle's tests
5 years ago
[[package]]
name = "proptest"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
version = "0.9.6"
Fix wiggle's tests
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
checksum = "01c477819b845fe023d33583ebf10c9f62518c8d79a0960ba5c36d6ac8a55a5b"
Fix wiggle's tests
5 years ago
dependencies = [
"bit-set",
"bitflags",
"byteorder",
"lazy_static",
"num-traits",
"quick-error",
"rand 0.6.5",
"rand_chacha 0.1.1",
"rand_xorshift",
"regex-syntax",
"rusty-fork",
"tempfile",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "quick-error"
Bump version to 0.9.0 (#790)
5 years ago
version = "1.2.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "quickcheck"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.9.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "a44883e74aa97ad63db83c4bf8ca490f02b2fc02f92575e720c8551e843c945f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
externref: Address review feedback
4 years ago
"env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
Fix wiggle's tests
5 years ago
"rand 0.7.3",
"rand_core 0.5.1",
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "quote"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
version = "1.0.7"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
checksum = "aa563d17ecb180e500da1cfd2b028310ac758de548efdd203e18f283af693f37"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rand"
version = "0.6.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d71dacdc3c88c1fde3885a3be3fbab9f35724e6ce99467f7d9c5026132184ca"
dependencies = [
"autocfg 0.1.7",
"libc",
"rand_chacha 0.1.1",
"rand_core 0.4.2",
"rand_hc 0.1.0",
"rand_isaac",
"rand_jitter",
"rand_os",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"rand_pcg 0.1.2",
Fix wiggle's tests
5 years ago
"rand_xorshift",
"winapi",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "rand"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.7.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"getrandom",
"libc",
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"rand_chacha 0.2.2",
Fix wiggle's tests
5 years ago
"rand_core 0.5.1",
"rand_hc 0.2.0",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"rand_pcg 0.2.1",
Fix wiggle's tests
5 years ago
]
[[package]]
name = "rand_chacha"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
dependencies = [
"autocfg 0.1.7",
"rand_core 0.3.1",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "rand_chacha"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
version = "0.2.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"ppv-lite86",
Fix wiggle's tests
5 years ago
"rand_core 0.5.1",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
dependencies = [
"rand_core 0.4.2",
]
[[package]]
name = "rand_core"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
dependencies = [
"getrandom",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rand_hc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
dependencies = [
"rand_core 0.3.1",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
dependencies = [
Fix wiggle's tests
5 years ago
"rand_core 0.5.1",
]
[[package]]
name = "rand_isaac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
dependencies = [
"rand_core 0.3.1",
]
[[package]]
name = "rand_jitter"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1166d5c91dc97b88d1decc3285bb0a99ed84b05cfd0bc2341bdf2d43fc41e39b"
dependencies = [
"libc",
"rand_core 0.4.2",
"winapi",
]
[[package]]
name = "rand_os"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
dependencies = [
"cloudabi",
"fuchsia-cprng",
"libc",
"rand_core 0.4.2",
"rdrand",
"winapi",
]
[[package]]
name = "rand_pcg"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "abf9b09b01790cfe0364f52bf32995ea3c39f4d2dd011eac241d2914146d0b44"
dependencies = [
"autocfg 0.1.7",
"rand_core 0.4.2",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
[[package]]
name = "rand_pcg"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "16abd0c1b639e9eb4d7c50c0b8100b0d0f849be2349829c740fe8e6eb4816429"
dependencies = [
"rand_core 0.5.1",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rand_xorshift"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
dependencies = [
"rand_core 0.3.1",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "raw-cpuid"
version = "7.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4a349ca83373cfa5d6dbb66fd76e58b2cca08da71a5f6400de0a0a6a9bceeaf"
dependencies = [
"bitflags",
"cc",
"rustc_version",
]
[[package]]
name = "rayon"
externref: Address review feedback
4 years ago
version = "1.3.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "62f02856753d04e03e26929f820d0a0a337ebe71f849801eea335d464b349080"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
externref: Address review feedback
4 years ago
"autocfg 1.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"crossbeam-deque",
"either",
"rayon-core",
]
[[package]]
name = "rayon-core"
externref: Address review feedback
4 years ago
version = "1.7.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "e92e15d89083484e11353891f1af602cc661426deb9564c298b270c726973280"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"crossbeam-deque",
"crossbeam-queue",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"crossbeam-utils",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"lazy_static",
"num_cpus",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
dependencies = [
"rand_core 0.3.1",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "redox_syscall"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.57"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "redox_users"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.3.4"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "09b23093265f8d200fa7b4c2c76297f47e681c655f6f1285a8780d6a022f7431"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"getrandom",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"redox_syscall",
"rust-argon2",
]
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
[[package]]
name = "regalloc"
Update to regalloc.rs 0.0.28. This version of regalloc.rs includes several bugfixes for reference-types support used by the new backend framework and the aarch64 backend (bytecodealliance/regalloc.rs#85 and bytecodealliance/regalloc.rs#86).
4 years ago
version = "0.0.28"
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to regalloc.rs 0.0.28. This version of regalloc.rs includes several bugfixes for reference-types support used by the new backend framework and the aarch64 backend (bytecodealliance/regalloc.rs#85 and bytecodealliance/regalloc.rs#86).
4 years ago
checksum = "3598bed0895fe0f72a9e0b00ef9e3a3c8af978a8401b2f2046dec5927de6364a"
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
dependencies = [
"log",
"rustc-hash",
mach backend: allow snapshotting IR graphs with the SNAPSHOT_REGALLOC env variable; This also requires the serde feature, which isn't enabled by default, thus it must be passed as a command-line argument to cargo.
4 years ago
"serde",
MachInst backend: pass through SourceLoc information. This change adds SourceLoc information per instruction in a `VCode<Inst>` container, and keeps this information up-to-date across register allocation and branch reordering. The information is initially collected during instruction lowering, eventually collected on the MachSection, and finally provided to the environment that wraps the codegen crate for wasmtime.
5 years ago
"smallvec",
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "regex"
externref: Address review feedback
4 years ago
version = "1.3.9"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "9c3780fcf44b193bc4d09f36d2a3c87b251da4a046c87795a0d35f4f927ad8e6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
"thread_local",
]
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "regex-automata"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae1ded71d66a4a97f5e961fd0cb25a5f366a42a41570d16a763a69c092c26ae4"
dependencies = [
"byteorder",
"regex-syntax",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "regex-syntax"
externref: Address review feedback
4 years ago
version = "0.6.18"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "26412eb97c6b088a6997e05f69403a802a92d520de2f8e63c2b65f9e0f47c4e8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "region"
externref: Address review feedback
4 years ago
version = "2.2.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "877e54ea2adcd70d80e9179344c97f93ef0dffd6b03e1f4529e6e83ab2fa9ae0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"bitflags",
"libc",
"mach",
"winapi",
]
[[package]]
name = "remove_dir_all"
externref: Address review feedback
4 years ago
version = "0.5.3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"winapi",
]
Move all examples to a top-level directory (#1286) * Move all examples to a top-level directory This commit moves all API examples (Rust and C) to a top-level `examples` directory. This is intended to make it more discoverable and conventional as to where examples are located. Additionally all examples are now available in both Rust and C to see how to execute the example in the language you're familiar with. The intention is that as more languages are supported we'd add more languages as examples here too. Each example is also accompanied by either a `*.wat` file which is parsed as input, or a Rust project in a `wasm` folder which is compiled as input. A simple driver crate was also added to `crates/misc` which executes all the examples on CI, ensuring the C and Rust examples all execute successfully.
5 years ago
[[package]]
name = "run-examples"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Move all examples to a top-level directory (#1286) * Move all examples to a top-level directory This commit moves all API examples (Rust and C) to a top-level `examples` directory. This is intended to make it more discoverable and conventional as to where examples are located. Additionally all examples are now available in both Rust and C to see how to execute the example in the language you're familiar with. The intention is that as more languages are supported we'd add more languages as examples here too. Each example is also accompanied by either a `*.wat` file which is parsed as input, or a Rust project in a `wasm` folder which is compiled as input. A simple driver crate was also added to `crates/misc` which executes all the examples on CI, ensuring the C and Rust examples all execute successfully.
5 years ago
dependencies = [
run-examples: Provide more error context for debugging Use `anyhow` for nice errors and provide error context on commands that we run.
4 years ago
"anyhow",
Move all examples to a top-level directory (#1286) * Move all examples to a top-level directory This commit moves all API examples (Rust and C) to a top-level `examples` directory. This is intended to make it more discoverable and conventional as to where examples are located. Additionally all examples are now available in both Rust and C to see how to execute the example in the language you're familiar with. The intention is that as more languages are supported we'd add more languages as examples here too. Each example is also accompanied by either a `*.wat` file which is parsed as input, or a Rust project in a `wasm` folder which is compiled as input. A simple driver crate was also added to `crates/misc` which executes all the examples on CI, ensuring the C and Rust examples all execute successfully.
5 years ago
"cc",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "rust-argon2"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.7.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "2bc8af4bda8e1ff4932523b94d3dd20ee30a87232323eda55903ffd71d2fb017"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
"base64 0.11.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"blake2b_simd",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"constant_time_eq",
"crossbeam-utils",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "rustc-demangle"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4c691c0e608126e00913e33f0ccf3727d5fc84573623b8d65b2df340b5201783"
ARM64 backend, part 3 / 11: MachInst infrastructure. This patch adds the MachInst, or Machine Instruction, infrastructure. This is the machine-independent portion of the new backend design. It contains the implementation of the "vcode" (virtual-registerized code) container, the top-level lowering algorithm and compilation pipeline, and the trait definitions that the machine backends will fill in. This backend infrastructure is included in the compilation of the `codegen` crate, but it is not yet tied into the public APIs; that patch will come last, after all the other pieces are filled in. This patch contains code written by Julian Seward <jseward@acm.org> and Benjamin Bouvier <public@benj.me>, originally developed on a side-branch before rebasing and condensing into this patch series. See the `arm64` branch at `https://github.com/cfallin/wasmtime` for original development history. Co-authored-by: Julian Seward <jseward@acm.org> Co-authored-by: Benjamin Bouvier <public@benj.me>
5 years ago
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
dependencies = [
"semver",
]
Fix wiggle's tests
5 years ago
[[package]]
name = "rusty-fork"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3dd93264e10c577503e926bd1430193eeb5d21b059148910082245309b424fae"
dependencies = [
"fnv",
"quick-error",
"tempfile",
"wait-timeout",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "ryu"
externref: Address review feedback
4 years ago
version = "1.0.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "scopeguard"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
version = "1.1.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "scroll"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "abb2332cb595d33f7edd5700f4cbf94892e680c7f0ae56adab58a35190b66cb1"
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"scroll_derive",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "scroll_derive"
externref: Address review feedback
4 years ago
version = "0.10.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "e367622f934864ffa1c704ba2b82280aab856e3d8213c84c5720257eb34b15b9"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
dependencies = [
"semver-parser",
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
[[package]]
name = "serde"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.114"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "5317f7588f0a5078ee60ef675ef96735a1442132dc645eb1d12c018620ed8cd3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.114"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "2a0be94b04690fbaed37cddffc5c134bf537c8e3329d53e982fe04c374978f8e"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "serde_json"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.56"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "3433e879a558dde8b5e8feb2a04899cf34fdde1fafb894687e52105fc1162ac3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"itoa",
"ryu",
"serde",
]
Implement customer [de]serialization for `IntegerInterner` Added some basic tests that the representation of the interner is only the `values` sequence, and that it round-trips successfully.
4 years ago
[[package]]
name = "serde_test"
version = "1.0.114"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f58190d074af17bd48118303db08afadbd506bc2ba511b4582cebd8f882a9b8d"
dependencies = [
"serde",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "sha2"
externref: Address review feedback
4 years ago
version = "0.8.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "a256f46ea78a0c0d9ff00077504903ac881a1dafdc20da66545699e7776b3e69"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"block-buffer",
"digest",
"fake-simd",
"opaque-debug",
]
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "sharded-slab"
version = "0.0.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "06d5a3f5166fb5b42a5439f2eee8b9de149e235961e3eb21c5808fc3ea17ff3e"
dependencies = [
"lazy_static",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "smallvec"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.4.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "3757cb9d89161a2f24e1cf78efa0c1fcff485d18e3f55e0aa3480824ddaa0f3f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "stable_deref_trait"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.2.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
[[package]]
name = "staticvec"
Switch CI back to nightly channel (#2014) * Switch CI back to nightly channel I think all upstream issues are now fixed so we should be good to switch back to nightly from our previously pinned version. * Fix doc warnings
4 years ago
version = "0.10.1"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch CI back to nightly channel (#2014) * Switch CI back to nightly channel I think all upstream issues are now fixed so we should be good to switch back to nightly from our previously pinned version. * Fix doc warnings
4 years ago
checksum = "ba02879e2cff631c9dad99168c191fa75201a263e159cc9669d3df58cb242093"
Integrate Lightbeam with latest Wasmtime master (#1232) * Implement trap info in Lightbeam * Start using wasm-reader instead of wasmparser for parsing operators * Update to use wasm-reader, some reductions in allocation, support source location tracking for traps, start to support multi-value The only thing that still needs to be supported for multi-value is stack returns, but we need to make it compatible with Cranelift. * Error when running out of registers (although we'd hope it should be impossible) instead of panicking * WIP: Update Lightbeam to work with latest Wasmtime * WIP: Update Lightbeam to use current wasmtime * WIP: Migrate to new system for builtin functions * WIP: Update Lightbeam to work with latest Wasmtime * Remove multi_mut * Format * Fix some bugs around arguments, add debuginfo offset tracking * Complete integration with new Wasmtime * Remove commented code * Fix formatting * Fix warnings, remove unused dependencies * Fix `iter` if there are too many elements, fix compilation for latest wasmtime * Fix float arguments on stack * Remove wasm-reader and trap info work * Allocate stack space _before_ passing arguments, fail if we can't zero a xmm reg * Fix stack argument offset calculation * Fix stack arguments in Lightbeam * Re-add WASI because it somehow got removed during rebase * Workaround for apparent `type_alias_impl_trait`-related bug in rustdoc * Fix breakages caused by rebase, remove module offset info as it is unrelated to wasmtime integration PR and was broken by rebase * Add TODO comment explaining `lightbeam::ModuleContext` trait
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "string-interner"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fd710eadff449a1531351b0e43eb81ea404336fa2f56c777427ab0e32a4cf183"
dependencies = [
"serde",
]
[[package]]
name = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
[[package]]
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
name = "structopt"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.3.15"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "de2f5e239ee807089b62adce73e48c625e0ed80df02c7ab3f068f5db5281065c"
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
dependencies = [
"clap",
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"lazy_static",
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
"structopt-derive",
]
[[package]]
name = "structopt-derive"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.4.8"
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "510413f9de616762a4fbeab62509bf15c729603b72d7cd71280fbca431b1c118"
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
dependencies = [
"heck",
"proc-macro-error",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
]
[[package]]
name = "syn"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.34"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "936cae2873c940d92e697597c5eee105fb570cd5689c695806f672883653349b"
Update fuzz crates (#826) * deps: Update to arbitrary 0.3.x and libfuzzer-sys 0.2.0 * ci: Use cargo-fuzz 0.7.x in CI
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"unicode-xid",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Bump version to 0.9.0 (#790)
5 years ago
[[package]]
name = "syn-mid"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
version = "0.5.0"
Bump version to 0.9.0 (#790)
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to cranelift 0.58.0 and enable (but ignore) reference types and bulk memory tests (#926) * Update cranelift to 0.58.0 * Update `wasmprinter` dep to require 0.2.1 We already had it in the lock file, but this ensures we won't ever go back down. * Ensure that our error messages match `assert_invalid`'s The bulk of this work was done in https://github.com/bytecodealliance/wasmparser/pull/186 but now we can test it at the `wasmtime` level as well. Fixes #492 * Stop feeling guilty about not matching `assert_malformed` messages Remove the "TODO" and stop printing warning messages. These would just be busy work to implement, and getting all the messages the exact same relies on using the same structure as the spec interpreter's parser, which means that where you have a helper function and they don't, then things go wrong, and vice versa. Not worth it. Fixes #492 * Enable (but ignore) the reference-types proposal tests * Match test suite directly, instead of roundabout starts/endswith * Enable (but ignore) bulk memory operations proposal test suite
5 years ago
checksum = "7be3539f6c128a931cf19dcee741c1af532c7fd387baa739c03dd2e96479338a"
Bump version to 0.9.0 (#790)
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Bump version to 0.9.0 (#790)
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "target-lexicon"
Update to the latest spec_testsuite and dependencies. (#803) * Update to the latest spec_testsuite and dependencies. Update to target-lexicon 0.10, cranelift 0.54, wast 0.6, faerie 0.14, and the latest spec_testsuite. For wast and cranelift-wasm, update the code for API changes. * Factor out the code for matching f32, f64, and v128. This takes the idea from #802 to split out `f32_matches`, `f64_matches`, and `v128_matches` functions, which better factor out the matching functionality between scalar and vector.
5 years ago
version = "0.10.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to the latest spec_testsuite and dependencies. (#803) * Update to the latest spec_testsuite and dependencies. Update to target-lexicon 0.10, cranelift 0.54, wast 0.6, faerie 0.14, and the latest spec_testsuite. For wast and cranelift-wasm, update the code for API changes. * Factor out the code for matching f32, f64, and v128. This takes the idea from #802 to split out `f32_matches`, `f64_matches`, and `v128_matches` functions, which better factor out the matching functionality between scalar and vector.
5 years ago
checksum = "ab0e7238dcc7b40a7be719a25365910f6807bd864f4cce6b2e6b873658e2b19d"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "tempfile"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
dependencies = [
"cfg-if",
"libc",
Fix wiggle's tests
5 years ago
"rand 0.7.3",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"redox_syscall",
"remove_dir_all",
"winapi",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "term"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0863a3345e70f61d613eab32ee046ccd1bcc5f9105fe402c61fcd0c13eeb8b5"
dependencies = [
"dirs",
"winapi",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "termcolor"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "1.1.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "bb6bfa289a4d7c5766392812c0a1f4c1ba45afa1ad47803c11e1f407d846d75f"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
"winapi-util",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
[[package]]
name = "terminal_size"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.13"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "9a14cd9f8c72704232f0bfc8455c0e861f0ad4eb60cc9ec8a170e231414c1e13"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
dependencies = [
"libc",
"winapi",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "termios"
Make Handle a trait required for any WASI-compatible handle (#1443) * Make Handle a trait required for any WASI-compatible handle OK, so this PR is a bit of an experiment that came about somewhat itself when I was looking at refactoring use of `Rc<RefCell<Descriptor>>` inside `Entry` struct. I've noticed that since we've placed `VirtualFile` on the same level as `OsHandle` and `Stdin` etc., we've ended up necessiitating checks for different combinations such as "is a real OS resource being mixed up with a virtual resource?", and if that was the case, we'd panic since this was clearly not allowed (e.g., symlinking, or worse renaming). Therefore, it seemed natural for virtual file to be on the same level as _any_ OS handle (regardless of whether it's an actual file, socket, or stdio handle). In other words, we should ideally envision the following hierarchy: ``` \-- OsHandle \-- OsFile -- Stdio \-- Virtual ``` This way, we can deal with the mix up at a level above which cleans up our logic significantly. On the other hand, when looking through the `virtfs`, the trait approach to some type that's a valid `Handle` grew on me, and I think this is the way to go. And this is what this PR is proposing, a trait `Handle` which features enough functionality to make both virtual and OS ops to work. Now, inside `Entry` we can safely store something like `Rc<dyn Handle>` where `Handle` can downcast to either `VirtualFile` or `VirtualDir`, or `OsHandle` if its an actual OS resource. Note that I've left `Handle` as one massive trait, but I reckon we could split it up into several smaller traits, each dealing with some bit of WASI functionality. I'm hoping this would perhaps make it easier to figure out polyfilling between snapshots and the new upcoming ephemeral snapshot since a lot of boilerplate functionality is now done as part of the `Handle` trait implementation. Next, I've redone the original `OsHandle` to be an `OsFile` which now stores a raw descriptor/handle (`RawFd`/`RawHandle`) inside a `Cell` so that we can handle interior mutability in an easy (read, non-panicky) way. In order not to lose the perks of derefercing to `std::fs::File`, I've added a convenience trait `AsFile` which will take `OsFile` by reference (or the stdio handles) and create a non-owned `ManuallyDrop<File>` resource which can be passed around and acted upon the way we'd normally do on `&File`. This change of course implies that we now have to worry about properly closing all OS resources stored as part of `OsFile`, thus this type now implements `Drop` trait which essentially speaking moves the raw descriptor/handle into a `File` and drops it. Finally, I've redone setting time info on relative paths on *nix using the same approach as advocated in the virtual fs. Namely, we do an `openat` followed by `filestat_set_times` on the obtained descriptor. This effectively removes the need for custom `filetime` module in `yanix`. However, this does probably incur additional cost of at least one additional syscall, and I haven't checked whether this approach performs as expected on platforms such as NixOS which as far as I remember had some weirdness todo with linking `utimensat` symbols, etc. Still, this change is worth considering given that the implementation of `path_filestat_set_times` cleans up a lot, albeit with some additional cost. * Fix tests on Windows * Address comments plus minor consistency cleanup * Address comments * Fix formatting
5 years ago
version = "0.3.2"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Make Handle a trait required for any WASI-compatible handle (#1443) * Make Handle a trait required for any WASI-compatible handle OK, so this PR is a bit of an experiment that came about somewhat itself when I was looking at refactoring use of `Rc<RefCell<Descriptor>>` inside `Entry` struct. I've noticed that since we've placed `VirtualFile` on the same level as `OsHandle` and `Stdin` etc., we've ended up necessiitating checks for different combinations such as "is a real OS resource being mixed up with a virtual resource?", and if that was the case, we'd panic since this was clearly not allowed (e.g., symlinking, or worse renaming). Therefore, it seemed natural for virtual file to be on the same level as _any_ OS handle (regardless of whether it's an actual file, socket, or stdio handle). In other words, we should ideally envision the following hierarchy: ``` \-- OsHandle \-- OsFile -- Stdio \-- Virtual ``` This way, we can deal with the mix up at a level above which cleans up our logic significantly. On the other hand, when looking through the `virtfs`, the trait approach to some type that's a valid `Handle` grew on me, and I think this is the way to go. And this is what this PR is proposing, a trait `Handle` which features enough functionality to make both virtual and OS ops to work. Now, inside `Entry` we can safely store something like `Rc<dyn Handle>` where `Handle` can downcast to either `VirtualFile` or `VirtualDir`, or `OsHandle` if its an actual OS resource. Note that I've left `Handle` as one massive trait, but I reckon we could split it up into several smaller traits, each dealing with some bit of WASI functionality. I'm hoping this would perhaps make it easier to figure out polyfilling between snapshots and the new upcoming ephemeral snapshot since a lot of boilerplate functionality is now done as part of the `Handle` trait implementation. Next, I've redone the original `OsHandle` to be an `OsFile` which now stores a raw descriptor/handle (`RawFd`/`RawHandle`) inside a `Cell` so that we can handle interior mutability in an easy (read, non-panicky) way. In order not to lose the perks of derefercing to `std::fs::File`, I've added a convenience trait `AsFile` which will take `OsFile` by reference (or the stdio handles) and create a non-owned `ManuallyDrop<File>` resource which can be passed around and acted upon the way we'd normally do on `&File`. This change of course implies that we now have to worry about properly closing all OS resources stored as part of `OsFile`, thus this type now implements `Drop` trait which essentially speaking moves the raw descriptor/handle into a `File` and drops it. Finally, I've redone setting time info on relative paths on *nix using the same approach as advocated in the virtual fs. Namely, we do an `openat` followed by `filestat_set_times` on the obtained descriptor. This effectively removes the need for custom `filetime` module in `yanix`. However, this does probably incur additional cost of at least one additional syscall, and I haven't checked whether this approach performs as expected on platforms such as NixOS which as far as I remember had some weirdness todo with linking `utimensat` symbols, etc. Still, this change is worth considering given that the implementation of `path_filestat_set_times` cleans up a lot, albeit with some additional cost. * Fix tests on Windows * Address comments plus minor consistency cleanup * Address comments * Fix formatting
5 years ago
checksum = "6f0fcee7b24a25675de40d5bb4de6e41b0df07bc9856295e7e2b3a3600c400c2"
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
dependencies = [
"libc",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "test-programs"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
"cfg-if",
"os_pipe",
bump witx dep to 0.8.5
5 years ago
"pretty_env_logger",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"tempfile",
"wasi-common",
"wasmtime",
"wasmtime-wasi",
"wat",
]
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
dependencies = [
"unicode-width",
]
[[package]]
name = "thiserror"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.20"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "7dfdd070ccd8ccb78f4ad66bf1982dc37f620ef696c6b5028fe2ed83dd3d0d08"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "1.0.20"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "bd80fc12f73063ac132ac92aceea36734f04a1d93c1240c6944e23a3b8841793"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "thread_local"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "1.0.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "d40c6d1b69745a6ec6fb1ca717914848da4b44ae29d9b3080cbee91d72a69b14"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"lazy_static",
]
wiggle: can swap in `tracing` for args
5 years ago
[[package]]
name = "time"
version = "0.1.43"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca8a50ef2360fbd1eeb0ecd46795a87a19024eb4b53c5dc916ca1fd95fe62438"
dependencies = [
"libc",
"winapi",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "toml"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
version = "0.5.6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Run `cargo update` on dependencies (#868) Looks like we're able to actually drop a good number of various deps, especially some large-ish ones like syn 0.14! Adding proc-macro2 v1.0.8 Adding syn v1.0.14 Removing base64 v0.10.1 Removing cloudabi v0.0.3 Removing crossbeam-utils v0.6.6 Removing failure v0.1.6 Removing failure_derive v0.1.6 Removing fuchsia-cprng v0.1.1 Removing proc-macro2 v0.4.30 Removing proc-macro2 v1.0.7 Removing quote v0.6.13 Removing rand_core v0.3.1 Removing rand_core v0.4.2 Removing rand_os v0.1.3 Removing rdrand v0.4.0 Removing syn v0.14.9 Removing syn v1.0.13 Removing synstructure v0.9.0 Removing unicode-xid v0.1.0 Removing wincolor v1.0.2 Updating arbitrary v0.3.2 -> v0.3.3 Updating arrayref v0.3.5 -> v0.3.6 Updating constant_time_eq v0.1.4 -> v0.1.5 Updating crates.io index Updating derive_arbitrary v0.3.1 -> v0.3.3 Updating indexmap v1.3.0 -> v1.3.1 Updating itoa v0.4.4 -> v0.4.5 Updating jobserver v0.1.18 -> v0.1.19 Updating memchr v2.2.1 -> v2.3.0 Updating num_cpus v1.11.1 -> v1.12.0 Updating proc-macro-error v0.4.4 -> v0.4.5 Updating proc-macro-error-attr v0.4.3 -> v0.4.5 Updating quickcheck v0.9.0 -> v0.9.2 Updating rand v0.7.2 -> v0.7.3 Updating redox_users v0.3.1 -> v0.3.4 Updating rust-argon2 v0.5.1 -> v0.7.0 Updating rustversion v1.0.1 -> v1.0.2 Updating serde_json v1.0.44 -> v1.0.45 Updating structopt v0.3.7 -> v0.3.8 Updating structopt-derive v0.4.0 -> v0.4.1 Updating termcolor v1.0.5 -> v1.1.0 Updating thread_local v1.0.0 -> v1.0.1 Updating toml v0.5.5 -> v0.5.6 Updating winapi-util v0.1.2 -> v0.1.3
5 years ago
checksum = "ffc92d160b1eef40665be3a05630d003936a3bc7da7421277846c2613e92c71a"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"serde",
]
temporarily use tracing from git
4 years ago
[[package]]
name = "tracing"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.16"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "c2e2a2de6b0d5cbb13fc21193a2296888eaab62b6044479aafb3c54c01c29fcd"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"cfg-if",
use tracing 0.1.15 release
4 years ago
"log",
"tracing-attributes",
"tracing-core",
wiggle: can swap in `tracing` for args
5 years ago
]
[[package]]
name = "tracing-attributes"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.9"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "f0693bf8d6f2bf22c690fc61a9d21ac69efdbb894a17ed596b9af0f01e64b84b"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "tracing-core"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.11"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "94ae75f0d28ae10786f3b1895c55fe72e79928fd5ccdebb5438c75e93fec178f"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"lazy_static",
]
[[package]]
name = "tracing-log"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5e0f8c7178e13481ff6765bd169b33e8d554c5d2bbede5e32c356194be02b9b9"
dependencies = [
"lazy_static",
"log",
use tracing 0.1.15 release
4 years ago
"tracing-core",
wiggle: can swap in `tracing` for args
5 years ago
]
[[package]]
name = "tracing-serde"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6ccba2f8f16e0ed268fc765d9b7ff22e965e7185d32f8f1ec8294fe17d86e79"
dependencies = [
"serde",
use tracing 0.1.15 release
4 years ago
"tracing-core",
wiggle: can swap in `tracing` for args
5 years ago
]
[[package]]
name = "tracing-subscriber"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.2.7"
wiggle: can swap in `tracing` for args
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "c72c8cf3ec4ed69fef614d011a5ae4274537a8a8c59133558029bd731eb71659"
wiggle: can swap in `tracing` for args
5 years ago
dependencies = [
"ansi_term",
"chrono",
"lazy_static",
"matchers",
"regex",
"serde",
"serde_json",
"sharded-slab",
"smallvec",
use tracing 0.1.15 release
4 years ago
"tracing-core",
wiggle: can swap in `tracing` for args
5 years ago
"tracing-log",
"tracing-serde",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "traitobject"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "efd1f82c56340fdf16f2a953d7bda4f8fdffba13d93b00844c25572110b26079"
[[package]]
name = "typemap"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "653be63c80a3296da5551e1bfd2cca35227e13cdd08c6668903ae2f4f77aa1f6"
dependencies = [
"unsafe-any",
]
[[package]]
name = "typenum"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
version = "1.12.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
checksum = "373c8a200f9e67a0c95e62a4f52fbf80c23b4381c05a17845531982fa99e6b33"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "unicode-segmentation"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e83e153d1053cbb5a118eeff7fd5be06ed99153f00dbcd8ae310c5fb2b22edc0"
[[package]]
name = "unicode-width"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.1.8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "unicode-xid"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.2.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "f7fe0bb3479651439c9112f72b6c505038574c9fbb575ed1bf3b797fa39dd564"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "unsafe-any"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f30360d7979f5e9c6e6cea48af192ea8fab4afb3cf72597154b8f08935bc9c7f"
dependencies = [
"traitobject",
]
[[package]]
name = "vec_map"
externref: Address review feedback
4 years ago
version = "0.8.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "version_check"
externref: Address review feedback
4 years ago
version = "0.9.2"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "b5a972e5669d67ba988ce3dc826706fb0a8b01471c088cb0b6110b805cc36aed"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
Fix wiggle's tests
5 years ago
[[package]]
name = "wait-timeout"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f200f5b12eb75f8c1ed65abd4b2db8a6e1b138a20de009dacee265a2498f3f6"
dependencies = [
"libc",
]
Fix build of cranelift-tools Accidentally left it out of the workspace members!
5 years ago
[[package]]
name = "walkdir"
version = "2.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "777182bc735b6424e1a57516d35ed72cb8019d85c8c9bf536dccb3445c1a2f7d"
dependencies = [
"same-file",
"winapi",
"winapi-util",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasi"
Bump version to 0.9.0 (#790)
5 years ago
version = "0.9.0+wasi-snapshot-preview1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump version to 0.9.0 (#790)
5 years ago
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasi-common"
Fixes needed for 0.19.0 (#2035) * Add some more wiggle crates to publish * Fix build of wasi-common on crates.io * Bump crates to 0.19.1 to fix crates.io build
4 years ago
version = "0.19.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
"cfg-if",
"cpu-time",
"filetime",
"getrandom",
"lazy_static",
"libc",
"log",
"thiserror",
"wig",
It's wiggle time! (#1202) * Use wiggle in place of wig in wasi-common This is a rather massive commit that introduces `wiggle` into the picture. We still use `wig`'s macro in `old` snapshot and to generate `wasmtime-wasi` glue, but everything else is now autogenerated by `wiggle`. In summary, thanks to `wiggle`, we no longer need to worry about serialising and deserialising to and from the guest memory, and all guest (WASI) types are now proper idiomatic Rust types. While we're here, in preparation for the ephemeral snapshot, I went ahead and reorganised the internal structure of the crate. Instead of modules like `hostcalls_impl` or `hostcalls_impl::fs`, the structure now resembles that in ephemeral with modules like `path`, `fd`, etc. Now, I'm not requiring we leave it like this, but I reckon it looks cleaner this way after all. * Fix wig to use new first-class access to caller's mem * Ignore warning in proc_exit for the moment * Group unsafes together in args and environ calls * Simplify pwrite; more unsafe blocks * Simplify fd_read * Bundle up unsafes in fd_readdir * Simplify fd_write * Add comment to path_readlink re zero-len buffers * Simplify unsafes in random_get * Hide GuestPtr<str> to &str in path::get * Rewrite pread and pwrite using SeekFrom and read/write_vectored I've left the implementation of VirtualFs pretty much untouched as I don't feel that comfortable in changing the API too much. Having said that, I reckon `pread` and `pwrite` could be refactored out, and `preadv` and `pwritev` could be entirely rewritten using `seek` and `read_vectored` and `write_vectored`. * Add comment about VirtFs unsafety * Fix all mentions of FdEntry to Entry * Fix warnings on Win * Add aux struct EntryTable responsible for Fds and Entries This commit adds aux struct `EntryTable` which is private to `WasiCtx` and is basically responsible for `Fd` alloc/dealloc as well as storing matching `Entry`s. This struct is entirely private to `WasiCtx` and as such as should remain transparent to `WasiCtx` users. * Remove redundant check for empty buffer in path_readlink * Preserve and rewind file cursor in pread/pwrite * Use GuestPtr<[u8]>::copy_from_slice wherever copying bytes directly * Use GuestPtr<[u8]>::copy_from_slice in fd_readdir * Clean up unsafes around WasiCtx accessors * Fix bugs in args_get and environ_get * Fix conflicts after rebase
5 years ago
"wiggle",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"winapi",
"winx",
"yanix",
]
Write ELF image and instantiate code_memory from it (#1931) - Create the ELF image from Compilation - Create CodeMemory from the ELF image - Link using ELF image - Remove creation of GDB JIT images from crates/debug - Move make_trampoline from compiler.rs
4 years ago
[[package]]
name = "wasmparser"
version = "0.57.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "32fddd575d477c6e9702484139cf9f23dcd554b06d185ed0f56c857dd3a47aa6"
Update `wasmparser` to 0.57.0
5 years ago
[[package]]
name = "wasmparser"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
version = "0.59.0"
Update `wasmparser` to 0.57.0
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
checksum = "a950e6a618f62147fd514ff445b2a0b53120d382751960797f85f058c7eda9b9"
Update `wasmparser` to 0.57.0
5 years ago
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasmprinter"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
version = "0.2.6"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
checksum = "334551eb8b0b1be16cf366a54ce9b541ac32a96e9b51e67ebbae1696f108f112"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "wasmtime"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Preserve full native stack traces in errors (#823) * Preserve full native stack traces in errors This commit builds on #759 by performing a few refactorings: * The `backtrace` crate is updated to 0.3.42 which incorporates the Windows-specific stack-walking code, so that's no longer needed. * A full `backtrace::Backtrace` type is held in a trap at all times. * The trap structures in the `wasmtime-*` internal crates were refactored a bit to preserve more information and deal with raw values rather than converting between various types and strings. * The `wasmtime::Trap` type has been updated with these various changes. Eventually I think we'll want to likely render full stack traces (and/or partial wasm ones) into error messages, but for now that's left as-is and we can always improve it later. I suspect the most relevant thing we need to do is to implement function name symbolication for wasm functions first, and then afterwards we can incorporate native function names! * Fix some test suite assertions
5 years ago
"backtrace",
Update Cargo.lock. Cargo.lock is checked into the repositoryu now, so we need to explicitly keep it up to date.
5 years ago
"cfg-if",
Improve handling of strings for backtraces (#843) * Improve handling of strings for backtraces Largely avoid storing strings at all in the `wasmtime-*` internal crates, and instead only store strings in a separate global cache specific to the `wasmtime` crate itself. This global cache is inserted and removed from dynamically as modules are created and deallocated, and the global cache is consulted whenever a `Trap` is created to symbolicate any wasm frames. This also avoids the need to thread `module_name` through the jit crates and back, and additionally removes the need for `ModuleSyncString`. * Run rustfmt
5 years ago
"lazy_static",
Update Cargo.lock. Cargo.lock is checked into the repositoryu now, so we need to explicitly keep it up to date.
5 years ago
"libc",
Linker refactoring (#1773) * Minor code tidying. * Document that `Linker::iter`'s iteration order is arbitrary. * Add a few more tests for `wasmtime::Linker`. * Refactor `Linker::compute_imports`. - Extract the error message generation into a separate function. - In the error message, sort the candidates. * Fix a typo in a comment. * Add `__rtti_base` to the list of allowed but deprecated exports. * Don't print an Error message when a program exits normally. * Update comments to reflect the current code. * Also allow "table" as an exported table, which is used by AssemblyScript.
5 years ago
"log",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"region",
Improve trap error messages (#831) * Improve trap error messages The new trap error message for the issue #828 looks like: ``` thread 'main' panicked at 'a', /proc/self/fd/11:1:13 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. Error: failed to run main module `test.wasm` Caused by: 0: failed to invoke `_start` 1: wasm trap: unreachable, source location: @6cea wasm backtrace: 0: __rust_start_panic 1: rust_panic 2: std::panicking::rust_panic_with_hook::h57f0cff11449798f 3: std::panicking::begin_panic::hd620695467c5dd1f 4: test::main::ha54db001eabbde1b 5: std::rt::lang_start::{{closure}}::h5acfb82693695869 6: std::sys_common::backtrace::__rust_begin_short_backtrace::h39e8b9420da241f9 7: std::panicking::try::do_call::hb7ebfcd70d5f703e 8: __rust_maybe_catch_panic 9: std::rt::lang_start_internal::hd5f64f52a5c5315c 10: std::rt::lang_start::h2a51d79994dd0c4b 11: __original_main 12: _start ``` Closes #828 * Tidy up the style of the traps tests * Add some tests and module names
5 years ago
"rustc-demangle",
Use smallvec for avoid allocations in the trampoline (#1965)
4 years ago
"smallvec",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Improve robustness of cache loading/storing (#974) * Improve robustness of cache loading/storing Today wasmtime incorrectly loads compiled compiled modules from the global cache when toggling settings such as optimizations. For example if you execute `wasmtime foo.wasm` that will cache globally an unoptimized version of the wasm module. If you then execute `wasmtime -O foo.wasm` it would then reload the unoptimized version from cache, not realizing the compilation settings were different, and use that instead. This can lead to very surprising behavior naturally! This commit updates how the cache is managed in an attempt to make it much more robust against these sorts of issues. This takes a leaf out of rustc's playbook and models the cache with a function that looks like: fn load<T: Hash>( &self, data: T, compute: fn(T) -> CacheEntry, ) -> CacheEntry; The goal here is that it guarantees that all the `data` necessary to `compute` the result of the cache entry is hashable and stored into the hash key entry. This was previously open-coded and manually managed where items were hashed explicitly, but this construction guarantees that everything reasonable `compute` could use to compile the module is stored in `data`, which is itself hashable. This refactoring then resulted in a few workarounds and a few fixes, including the original issue: * The `Module` type was split into `Module` and `ModuleLocal` where only the latter is hashed. The previous hash function for a `Module` left out items like the `start_func` and didn't hash items like the imports of the module. Omitting the `start_func` was fine since compilation didn't actually use it, but omitting imports seemed uncomfortable because while compilation didn't use the import values it did use the *number* of imports, which seems like it should then be put into the cache key. The `ModuleLocal` type now derives `Hash` to guarantee that all of its contents affect the hash key. * The `ModuleTranslationState` from `cranelift-wasm` doesn't implement `Hash` which means that we have a manual wrapper to work around that. This will be fixed with an upstream implementation, since this state affects the generated wasm code. Currently this is just a map of signatures, which is present in `Module` anyway, so we should be good for the time being. * Hashing `dyn TargetIsa` was also added, where previously it was not fully hashed. Previously only the target name was used as part of the cache key, but crucially the flags of compilation were omitted (for example the optimization flags). Unfortunately the trait object itself is not hashable so we still have to manually write a wrapper to hash it, but we likely want to add upstream some utilities to hash isa objects into cranelift itself. For now though we can continue to add hashed fields as necessary. Overall the goal here was to use the compiler to expose what we're not hashing, and then make sure we organize data and write the right code to ensure everything is hashed, and nothing more. * Update crates/environ/src/module.rs Co-Authored-By: Peter Huene <peterhuene@protonmail.com> * Fix lightbeam * Fix compilation of tests * Update the expected structure of the cache * Revert "Update the expected structure of the cache" This reverts commit 2b53fee426a4e411c313d8c1e424841ba304a9cd. * Separate the cache dir a bit * Add a test the cache is busted with opt levels * rustfmt Co-authored-by: Peter Huene <peterhuene@protonmail.com>
5 years ago
"tempfile",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-environ",
"wasmtime-jit",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
"wasmtime-profiling",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-runtime",
Expand top-level `wasmtime` crate docs (#1955) This is something I meant to do a long time ago but forgot to get around to it! This commit updates the top-level documentation of the `wasmtime` crate to have examples, more words, and generall be a bit more up-to-date and complete.
4 years ago
"wasmtime-wasi",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wat",
Update Cargo.lock. Cargo.lock is checked into the repositoryu now, so we need to explicitly keep it up to date.
5 years ago
"winapi",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
Move the C API to a separate crate (#818) * Move the C API to a separate crate This commit moves the C API from `crates/api/src/wasm.rs` to `crates/capi/src/lib.rs` to be located in a separate crate. There's a number of reasons for this: * When a Rust program depends on the `wasmtime` crate, there's no need to compile in the C API. * This should improve compile times of the `wasmtime` crate since it's not producing artifacts which aren't always used. * The development of the C API can be guaranteed to only use the public API of the `wasmtime` crate itself. Some CI pieces are tweaked and this overall shouldn't have much impact on users, it's intended that it's a cleanup/speedup for developers! * Disable rustdoc/tests for capi * Review feedback * Add back in accidentally deleted comment * More renamings * Try to fix dotnet build
5 years ago
[[package]]
name = "wasmtime-c-api"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Move the C API to a separate crate (#818) * Move the C API to a separate crate This commit moves the C API from `crates/api/src/wasm.rs` to `crates/capi/src/lib.rs` to be located in a separate crate. There's a number of reasons for this: * When a Rust program depends on the `wasmtime` crate, there's no need to compile in the C API. * This should improve compile times of the `wasmtime` crate since it's not producing artifacts which aren't always used. * The development of the C API can be guaranteed to only use the public API of the `wasmtime` crate itself. Some CI pieces are tweaked and this overall shouldn't have much impact on users, it's intended that it's a cleanup/speedup for developers! * Disable rustdoc/tests for capi * Review feedback * Add back in accidentally deleted comment * More renamings * Try to fix dotnet build
5 years ago
dependencies = [
Add a `wasmtime::Linker` type (#1384) * Add a `wasmtime::Linker` type This commit adds a new type to the `wasmtime` crate, a `Linker`. This linker is intended to vastly simplify calling `Instance::new` by easily performing name resolution and incrementally defining state over time. The goal here is to start down a path of making linking wasm modules in `wasmtime` a first-class and ergonomic operation. This is highly likely to evolve over time and get tweaked through releases as we iterate towards a design well-suited for `wasmtime`, but this is intended to at least be the initial foundation for such functionality. This commit additionally also adds a C API for the linker and switches the existing linking examples to using this linker in both Rust and C. One piece of future work I'd like to tackle next is to integrate WASI into the `wasmtime` crate in a more first-class manner. This [`Linker`] type provides a great location to hook into the instantiation process to easily instantiate modules with WASI imports. That's a relatively large refactoring for now though and I figured it'd be best left for a different time. Closes #727
5 years ago
"anyhow",
externref: Address review feedback
4 years ago
"env_logger",
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
"once_cell",
Implement WASI C API. This commit implements an initial WASI C API that can be used to instantiate and configure a WASI instance from C. This also implements a `WasiBuilder` for the C# API enabling .NET hosts to bind to Wasmtime's WASI implementation.
5 years ago
"wasi-common",
Move the C API to a separate crate (#818) * Move the C API to a separate crate This commit moves the C API from `crates/api/src/wasm.rs` to `crates/capi/src/lib.rs` to be located in a separate crate. There's a number of reasons for this: * When a Rust program depends on the `wasmtime` crate, there's no need to compile in the C API. * This should improve compile times of the `wasmtime` crate since it's not producing artifacts which aren't always used. * The development of the C API can be guaranteed to only use the public API of the `wasmtime` crate itself. Some CI pieces are tweaked and this overall shouldn't have much impact on users, it's intended that it's a cleanup/speedup for developers! * Disable rustdoc/tests for capi * Review feedback * Add back in accidentally deleted comment * More renamings * Try to fix dotnet build
5 years ago
"wasmtime",
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
"wasmtime-c-api-macros",
Implement WASI C API. This commit implements an initial WASI C API that can be used to instantiate and configure a WASI instance from C. This also implements a `WasiBuilder` for the C# API enabling .NET hosts to bind to Wasmtime's WASI implementation.
5 years ago
"wasmtime-wasi",
Add a wasmtime-specific `wasmtime_wat2wasm` C API (#1206) * Add a wasmtime-specific `wasmtime_wat2wasm` C API This commit implements a wasmtime-specific C API for converting the text format to the binary format. An upstream spec issue exists for adding this to the C API, but in the meantime we can experiment with our own version of this API and use it in the C# extension, for example! Closes #1000 * Reorder arguments * Use wasm_byte_vec_t for input `*.wat` * Mark wat input as const * Return an error message and use `fixed` * Actually include the error message * Use `fixed` in `Module.cs` as well
5 years ago
"wat",
Move the C API to a separate crate (#818) * Move the C API to a separate crate This commit moves the C API from `crates/api/src/wasm.rs` to `crates/capi/src/lib.rs` to be located in a separate crate. There's a number of reasons for this: * When a Rust program depends on the `wasmtime` crate, there's no need to compile in the C API. * This should improve compile times of the `wasmtime` crate since it's not producing artifacts which aren't always used. * The development of the C API can be guaranteed to only use the public API of the `wasmtime` crate itself. Some CI pieces are tweaked and this overall shouldn't have much impact on users, it's intended that it's a cleanup/speedup for developers! * Disable rustdoc/tests for capi * Review feedback * Add back in accidentally deleted comment * More renamings * Try to fix dotnet build
5 years ago
]
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
[[package]]
name = "wasmtime-c-api-macros"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Refactor and fill out wasmtime's C API (#1415) * Refactor and improve safety of C API This commit is intended to be a relatively large refactoring of the C API which is targeted at improving the safety of our C API definitions. Not all of the APIs have been updated yet but this is intended to be the start. The goal here is to make as many functions safe as we can, expressing inputs/outputs as native Rust types rather than raw pointers wherever possible. For example instead of `*const wasm_foo_t` we'd take `&wasm_foo_t`. Instead of returning `*mut wasm_foo_t` we'd return `Box<wasm_foo_t>`. No ABI/API changes are intended from this commit, it's supposed to only change how we define all these functions internally. This commit also additionally implements a few more API bindings for exposed vector types by unifying everything into one macro. Finally, this commit moves many internal caches in the C API to the `OnceCell` type which provides a safe interface for one-time initialization. * Split apart monolithic C API `lib.rs` This commit splits the monolithic `src/lib.rs` in the C API crate into lots of smaller files. The goal here is to make this a bit more readable and digestable. Each module now contains only API bindings for a particular type, roughly organized around the grouping in the wasm.h header file already. A few more extensions were added, such as filling out `*_as_*` conversions with both const and non-const versions. Additionally many APIs were made safer in the same style as the previous commit, generally preferring Rust types rather than raw pointer types. Overall no functional change is intended here, it should be mostly just code movement and minor refactorings! * Make a few wasi C bindings safer Use safe Rust types where we can and touch up a few APIs here and there. * Implement `wasm_*type_as_externtype*` APIs This commit restructures `wasm_externtype_t` to be similar to `wasm_extern_t` so type conversion between the `*_extern_*` variants to the concrete variants are all simple casts. (checked in the case of general to concrete, of course). * Consistently imlpement host info functions in the API This commit adds a small macro crate which is then used to consistently define the various host-info-related functions in the C API. The goal here is to try to mirror what the `wasm.h` header provides to provide a full implementation of the header.
5 years ago
dependencies = [
"proc-macro2",
"quote",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasmtime-cli"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
externref: Address review feedback
4 years ago
"env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"file-per-thread-logger",
Test basic DWARF generation (#931) * Add obj generation with debug info * Add simple transform check
5 years ago
"filecheck",
Implement interrupting wasm code, reimplement stack overflow (#1490) * Implement interrupting wasm code, reimplement stack overflow This commit is a relatively large change for wasmtime with two main goals: * Primarily this enables interrupting executing wasm code with a trap, preventing infinite loops in wasm code. Note that resumption of the wasm code is not a goal of this commit. * Additionally this commit reimplements how we handle stack overflow to ensure that host functions always have a reasonable amount of stack to run on. This fixes an issue where we might longjmp out of a host function, skipping destructors. Lots of various odds and ends end up falling out in this commit once the two goals above were implemented. The strategy for implementing this was also lifted from Spidermonkey and existing functionality inside of Cranelift. I've tried to write up thorough documentation of how this all works in `crates/environ/src/cranelift.rs` where gnarly-ish bits are. A brief summary of how this works is that each function and each loop header now checks to see if they're interrupted. Interrupts and the stack overflow check are actually folded into one now, where function headers check to see if they've run out of stack and the sentinel value used to indicate an interrupt, checked in loop headers, tricks functions into thinking they're out of stack. An interrupt is basically just writing a value to a location which is read by JIT code. When interrupts are delivered and what triggers them has been left up to embedders of the `wasmtime` crate. The `wasmtime::Store` type has a method to acquire an `InterruptHandle`, where `InterruptHandle` is a `Send` and `Sync` type which can travel to other threads (or perhaps even a signal handler) to get notified from. It's intended that this provides a good degree of flexibility when interrupting wasm code. Note though that this does have a large caveat where interrupts don't work when you're interrupting host code, so if you've got a host import blocking for a long time an interrupt won't actually be received until the wasm starts running again. Some fallout included from this change is: * Unix signal handlers are no longer registered with `SA_ONSTACK`. Instead they run on the native stack the thread was already using. This is possible since stack overflow isn't handled by hitting the guard page, but rather it's explicitly checked for in wasm now. Native stack overflow will continue to abort the process as usual. * Unix sigaltstack management is now no longer necessary since we don't use it any more. * Windows no longer has any need to reset guard pages since we no longer try to recover from faults on guard pages. * On all targets probestack intrinsics are disabled since we use a different mechanism for catching stack overflow. * The C API has been updated with interrupts handles. An example has also been added which shows off how to interrupt a module. Closes #139 Closes #860 Closes #900 * Update comment about magical interrupt value * Store stack limit as a global value, not a closure * Run rustfmt * Handle review comments * Add a comment about SA_ONSTACK * Use `usize` for type of `INTERRUPTED` * Parse human-readable durations * Bring back sigaltstack handling Allows libstd to print out stack overflow on failure still. * Add parsing and emission of stack limit-via-preamble * Fix new example for new apis * Fix host segfault test in release mode * Fix new doc example
5 years ago
"humantime",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"libc",
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
"log",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"more-asserts",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
bump witx dep to 0.8.5
5 years ago
"pretty_env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"rayon",
Use structopt instead of docopt. This commit refactors the Wasmtime CLI tools to use `structopt` instead of `docopt`. The `wasmtime` tool now has the following subcommands: * `config new` - creates a new Wasmtime configuration file. * `run` - runs a WebAssembly module. * `wasm2obj` - translates a Wasm module to native object file. * `wast` - runs a test script file. If no subcommand is specified, the `run` subcommand is used. Thus, `wasmtime foo.wasm` should continue to function as expected. The `wasm2obj` and `wast` tools still exist, but delegate to the same implementation as the `wasmtime` subcommands. The standalone `wasm2obj` and `wast` tools may be removed in the future in favor of simply using `wasmtime`. Included in this commit is a breaking change to the default Wasmtime configuration file: it has been renamed from `wasmtime-cache-config.toml` to simply `config.toml`. The new name is less specific which will allow for additional (non-cache-related) settings in the future. There are some breaking changes to improve command line UX: * The `--cache-config` option has been renamed to `--config`. * The `--create-config-file` option has moved to the `config new` subcommand. As a result, the `wasm2obj` and `wast` tools cannot be used to create a new config file. * The short form of the `--optimize` option has changed from `-o` to `-O` for consistency. * The `wasm2obj` command takes the output object file as a required positional argument rather than the former required output *option* (e.g. `wasmtime wasm2obj foo.wasm foo.obj`).
5 years ago
"structopt",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Fix 'not enough arguments' during wasmtime run (#858) * Fix 'not enough arguments' during wasmtime run * add simple cli smoke tests * autogenerate wasm
5 years ago
"tempfile",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"test-programs",
"wasi-common",
"wasmtime",
"wasmtime-debug",
"wasmtime-environ",
Move most wasmtime tests into one test suite (#1544) * Move most wasmtime tests into one test suite This commit moves most wasmtime tests into a single test suite which gets compiled into one executable instead of having lots of test executables. The goal here is to reduce disk space on CI, and this should be achieved by having fewer executables which means fewer copies of `libwasmtime.rlib` linked across binaries on the system. More importantly though this means that DWARF debug information should only be in one executable rather than duplicated across many. * Share more build caches Globally set `RUSTFLAGS` to `-Dwarnings` instead of individually so all build steps share the same value. * Allow some dead code in cranelift-codegen Prevents having to fix all warnings for all possible feature combinations, only the main ones which come up. * Update some debug file paths
5 years ago
"wasmtime-fuzzing",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-jit",
"wasmtime-obj",
Add missing dev-dependency: wasmtime-runtime
5 years ago
"wasmtime-runtime",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-wasi",
"wasmtime-wast",
"wat",
]
[[package]]
name = "wasmtime-debug"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.21.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"more-asserts",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-environ",
]
[[package]]
name = "wasmtime-environ"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Remove usage of `CompilationStrategy` from `Config` (#764) * Remove usage of `CompilationStrategy` from `Config` This commit removes the public API usage of the internal `CompilationStrategy` enumeration from the `Config` type in the `wasmtime` crate. To do this the `enum` was copied locally into the crate and renamed `Strategy`. The high-level description of this change is: * The `Config::strategy` method now takes a locally-defined `Strategy` enumeration instead of an internal type. * The contents of `Strategy` are always the same, not relying on Cargo features to indicate which variants are present. This avoids unnecessary downstream `#[cfg]`. * A `lightbeam` feature was added to the `wasmtime` crate itself to lightbeam compilation support. * The `Config::strategy` method is now fallible. It returns a runtime error if support for the selected strategy wasn't compiled in. * The `Strategy` enum is listed as `#[non_exhaustive]` so we can safely add variants over time to it. This reduces the public crate dependencies of the `wasmtime` crate itself, removing the need to reach into internal crates even more! cc #708 * Fix fuzz targets * Update nightly used to build releases * Run rustfmt
5 years ago
"anyhow",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"base64 0.12.3",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"bincode",
wasmtime: add build-time option for parallel compilation (#1903) When running in embedded environments, threads creation is sometimes undesirable. This adds a feature to toggle wasmtime's internal thread creation for parallel compilation.
4 years ago
"cfg-if",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cranelift-codegen",
"cranelift-entity",
wasmtime: Implement `table.get` and `table.set` These instructions have fast, inline JIT paths for the common cases, and only call out to host VM functions for the slow paths. This required some changes to `cranelift-wasm`'s `FuncEnvironment`: instead of taking a `FuncCursor` to insert an instruction sequence within the current basic block, `FuncEnvironment::translate_table_{get,set}` now take a `&mut FunctionBuilder` so that they can create whole new basic blocks. This is necessary for implementing GC read/write barriers that involve branching (e.g. checking for null, or whether a store buffer is at capacity). Furthermore, it required that the `load`, `load_complex`, and `store` instructions handle loading and storing through an `r{32,64}` rather than just `i{32,64}` addresses. This involved making `r{32,64}` types acceptable instantiations of the `iAddr` type variable, plus a few new instruction encodings. Part of #929
4 years ago
"cranelift-frontend",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cranelift-wasm",
"directories",
"errno",
"file-per-thread-logger",
"filetime",
"indexmap",
"lazy_static",
"libc",
"lightbeam",
"log",
"more-asserts",
bump witx dep to 0.8.5
5 years ago
"pretty_env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"rayon",
"serde",
"sha2",
"tempfile",
"thiserror",
"toml",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"winapi",
"zstd",
]
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
[[package]]
name = "wasmtime-fuzz"
Wasmtime 0.13.0 and Cranelift 0.61.0. (#1398) This also updates the publishing scripts to work with newly added and reorganized crates.
5 years ago
version = "0.0.0"
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
dependencies = [
Merge cranelift/wasmtime fuzzing
5 years ago
"cranelift-codegen",
"cranelift-reader",
"cranelift-wasm",
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
"libfuzzer-sys",
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
"peepmatic-fuzzing",
Merge cranelift/wasmtime fuzzing
5 years ago
"target-lexicon",
Remove usage of `CompilationStrategy` from `Config` (#764) * Remove usage of `CompilationStrategy` from `Config` This commit removes the public API usage of the internal `CompilationStrategy` enumeration from the `Config` type in the `wasmtime` crate. To do this the `enum` was copied locally into the crate and renamed `Strategy`. The high-level description of this change is: * The `Config::strategy` method now takes a locally-defined `Strategy` enumeration instead of an internal type. * The contents of `Strategy` are always the same, not relying on Cargo features to indicate which variants are present. This avoids unnecessary downstream `#[cfg]`. * A `lightbeam` feature was added to the `wasmtime` crate itself to lightbeam compilation support. * The `Config::strategy` method is now fallible. It returns a runtime error if support for the selected strategy wasn't compiled in. * The `Strategy` enum is listed as `#[non_exhaustive]` so we can safely add variants over time to it. This reduces the public crate dependencies of the `wasmtime` crate itself, removing the need to reach into internal crates even more! cc #708 * Fix fuzz targets * Update nightly used to build releases * Run rustfmt
5 years ago
"wasmtime",
Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721
5 years ago
"wasmtime-fuzzing",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasmtime-fuzzing"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Update to arbitrary@0.4.0 and libfuzzer-sys@0.3.1
5 years ago
"arbitrary",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"binaryen",
externref: Address review feedback
4 years ago
"env_logger",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
Limit rayon to one thread during fuzzing This should enable more deterministic execution.
5 years ago
"rayon",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmprinter",
"wasmtime",
Add a spec test fuzzer for Config (#1509) * Add a spec test fuzzer for Config This commit adds a new fuzzer which is intended to run on oss-fuzz. This fuzzer creates and arbitrary `Config` which *should* pass spec tests and then asserts that it does so. The goal here is to weed out any accidental bugs in global configuration which could cause non-spec-compliant behavior. * Move implementation to `fuzzing` crate
5 years ago
"wasmtime-wast",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wat",
]
[[package]]
name = "wasmtime-jit"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Use __chkstk for aarch64 instead of __rust_probestack. (#800) * Use __chkstk for aarch64 instead of __rust_probestack. * Demote rustdoc to a regular comment to fix the build.
5 years ago
"cfg-if",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cranelift-codegen",
"cranelift-entity",
"cranelift-frontend",
"cranelift-native",
"cranelift-wasm",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.21.0",
Handle select relocations while generating trampolines (#1347) * Handle select relocations while generating trampolines Trampoline generation for all function signatures exposed a preexisting bug in wasmtime where trampoline generation occasionally does have relocations, but it's asserted that trampolines don't generate relocations, causing a panic. The relocation is currently primarily the probestack function which happens when functions might have a huge number of parameters, but not so huge as to blow the wasmparser limit of how many parameters are allowed. This commit fixes the issue by handling relocations for trampolines in the same manner as the rest of the code. Note that dynamically-generated trampolines via the `Func` API still panic if they have too many arguments and generate a relocation, but it seems like we can try to fix that later if the need truly arises. Closes #1322 * Log trampoline relocations
5 years ago
"log",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"more-asserts",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"region",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wasmparser 0.59.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-debug",
"wasmtime-environ",
Removes duplicate code in src/obj.rs, crates/obj and crates/jit/object.rs (#1993) Changes: - Moves object creation code from crates/jit/object.rs to the creates/obj (as ObjectBuilder) - Removes legacy crates/obj/function.rs - Removes write_debugsections
4 years ago
"wasmtime-obj",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
"wasmtime-profiling",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-runtime",
"winapi",
]
[[package]]
name = "wasmtime-obj"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Remove usage of `CompilationStrategy` from `Config` (#764) * Remove usage of `CompilationStrategy` from `Config` This commit removes the public API usage of the internal `CompilationStrategy` enumeration from the `Config` type in the `wasmtime` crate. To do this the `enum` was copied locally into the crate and renamed `Strategy`. The high-level description of this change is: * The `Config::strategy` method now takes a locally-defined `Strategy` enumeration instead of an internal type. * The contents of `Strategy` are always the same, not relying on Cargo features to indicate which variants are present. This avoids unnecessary downstream `#[cfg]`. * A `lightbeam` feature was added to the `wasmtime` crate itself to lightbeam compilation support. * The `Config::strategy` method is now fallible. It returns a runtime error if support for the selected strategy wasn't compiled in. * The `Strategy` enum is listed as `#[non_exhaustive]` so we can safely add variants over time to it. This reduces the public crate dependencies of the `wasmtime` crate itself, removing the need to reach into internal crates even more! cc #708 * Fix fuzz targets * Update nightly used to build releases * Run rustfmt
5 years ago
"anyhow",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"more-asserts",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.20.0",
Removes duplicate code in src/obj.rs, crates/obj and crates/jit/object.rs (#1993) Changes: - Moves object creation code from crates/jit/object.rs to the creates/obj (as ObjectBuilder) - Removes legacy crates/obj/function.rs - Removes write_debugsections
4 years ago
"target-lexicon",
"wasmtime-debug",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"wasmtime-environ",
]
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
[[package]]
name = "wasmtime-profiling"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
dependencies = [
Enable jitdump profiling support by default (#1310) * Enable jitdump profiling support by default This the result of some of the investigation I was doing for #1017. I've done a number of refactorings here which culminated in a number of changes that all amount to what I think should result in jitdump support being enabled by default: * Pass in a list of finished functions instead of just a range to ensure that we're emitting jit dump data for a specific module rather than a whole `CodeMemory` which may have other modules. * Define `ProfilingStrategy` in the `wasmtime` crate to have everything locally-defined * Add support to the C API to enable profiling * Documentation added for profiling with jitdump to the book * Split out supported/unsupported files in `jitdump.rs` to avoid having lots of `#[cfg]`. * Make dependencies optional that are only used for `jitdump`. * Move initialization up-front to `JitDumpAgent::new()` instead of deferring it to the first module. * Pass around `Arc<dyn ProfilingAgent>` instead of `Option<Arc<Mutex<Box<dyn ProfilingAgent>>>>` The `jitdump` Cargo feature is now enabled by default which means that our published binaries, C API artifacts, and crates will support profiling at runtime by default. The support I don't think is fully fleshed out and working but I think it's probably in a good enough spot we can get users playing around with it!
5 years ago
"anyhow",
"cfg-if",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"gimli 0.21.0",
Adds JIT profiling support for VTune (#819) This patch adds initial support for ittapi which is an open source profiling api for instrumentation and tracing and profiling of jitted code. Result files can be read by VTune for analysis Build: cargo build --features=vtune Profile: // Using amplxe-cl from VTune amplxe-cl -v -collect hostpost target/debug/wasmtime --vtune test.wasm
5 years ago
"ittapi-rs",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
"lazy_static",
"libc",
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
"object 0.19.0",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"scroll",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
"serde",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"target-lexicon",
Enable jitdump profiling support by default (#1310) * Enable jitdump profiling support by default This the result of some of the investigation I was doing for #1017. I've done a number of refactorings here which culminated in a number of changes that all amount to what I think should result in jitdump support being enabled by default: * Pass in a list of finished functions instead of just a range to ensure that we're emitting jit dump data for a specific module rather than a whole `CodeMemory` which may have other modules. * Define `ProfilingStrategy` in the `wasmtime` crate to have everything locally-defined * Add support to the C API to enable profiling * Documentation added for profiling with jitdump to the book * Split out supported/unsupported files in `jitdump.rs` to avoid having lots of `#[cfg]`. * Make dependencies optional that are only used for `jitdump`. * Move initialization up-front to `JitDumpAgent::new()` instead of deferring it to the first module. * Pass around `Arc<dyn ProfilingAgent>` instead of `Option<Arc<Mutex<Box<dyn ProfilingAgent>>>>` The `jitdump` Cargo feature is now enabled by default which means that our published binaries, C API artifacts, and crates will support profiling at runtime by default. The support I don't think is fully fleshed out and working but I think it's probably in a good enough spot we can get users playing around with it!
5 years ago
"wasmtime-environ",
"wasmtime-runtime",
Adds perf jitdump support (#360) Patch adds support for the perf jitdump file specification. With this patch it should be possible to see profile data for code generated and maped at runtime. Specifically the patch adds support for the JIT_CODE_LOAD and the JIT_DEBUG_INFO record as described in the specification. Dumping jitfiles is enabled with the --jitdump flag. When the -g flag is also used there is an attempt to dump file and line number information where this option would be most useful when the WASM file already includes DWARF debug information. The generation of the jitdump files has been tested on only a few wasm files. This patch is expected to be useful/serviceable where currently there is no means for jit profiling, but future patches may benefit line mapping and add support for additional jitdump record types. Usage Example: Record sudo perf record -k 1 -e instructions:u target/debug/wasmtime -g --jitdump test.wasm Combine sudo perf inject -v -j -i perf.data -o perf.jit.data Report sudo perf report -i perf.jit.data -F+period,srcline
5 years ago
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wasmtime-runtime"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Backtrace WebAssembly function JIT frames (#759) * Create backtrace * Extend unwind information with FDE data. * Expose backtrace via API/Trap * wasmtime_call returns not-str * Return Arc<JITFrameTag> * rename frame -> function * Fix windows crashes and unwrap UNWIND_HISTORY_TABLE * mmaps -> entries * pass a backtrace in ActionOutcome * add test_trap_stack_overflow * Update cranelift version.
5 years ago
"backtrace",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"cc",
Update Cargo.lock. Cargo.lock is checked into the repositoryu now, so we need to explicitly keep it up to date.
5 years ago
"cfg-if",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"indexmap",
Disconnects `Store` state fields from `Compiler` (#1761) * Moves CodeMemory, VMInterrupts and SignatureRegistry from Compiler * CompiledModule holds CodeMemory and GdbJitImageRegistration * Store keeps track of its JIT code * Makes "jit_int.rs" stuff Send+Sync * Adds the threads example.
4 years ago
"lazy_static",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"libc",
externref: implement stack map-based garbage collection For host VM code, we use plain reference counting, where cloning increments the reference count, and dropping decrements it. We can avoid many of the on-stack increment/decrement operations that typically plague the performance of reference counting via Rust's ownership and borrowing system. Moving a `VMExternRef` avoids mutating its reference count, and borrowing it either avoids the reference count increment or delays it until if/when the `VMExternRef` is cloned. When passing a `VMExternRef` into compiled Wasm code, we don't want to do reference count mutations for every compiled `local.{get,set}`, nor for every function call. Therefore, we use a variation of **deferred reference counting**, where we only mutate reference counts when storing `VMExternRef`s somewhere that outlives the activation: into a global or table. Simultaneously, we over-approximate the set of `VMExternRef`s that are inside Wasm function activations. Periodically, we walk the stack at GC safe points, and use stack map information to precisely identify the set of `VMExternRef`s inside Wasm activations. Then we take the difference between this precise set and our over-approximation, and decrement the reference count for each of the `VMExternRef`s that are in our over-approximation but not in the precise set. Finally, the over-approximation is replaced with the precise set. The `VMExternRefActivationsTable` implements the over-approximized set of `VMExternRef`s referenced by Wasm activations. Calling a Wasm function and passing it a `VMExternRef` moves the `VMExternRef` into the table, and the compiled Wasm function logically "borrows" the `VMExternRef` from the table. Similarly, `global.get` and `table.get` operations clone the gotten `VMExternRef` into the `VMExternRefActivationsTable` and then "borrow" the reference out of the table. When a `VMExternRef` is returned to host code from a Wasm function, the host increments the reference count (because the reference is logically "borrowed" from the `VMExternRefActivationsTable` and the reference count from the table will be dropped at the next GC). For more general information on deferred reference counting, see *An Examination of Deferred Reference Counting and Cycle Detection* by Quinane: https://openresearch-repository.anu.edu.au/bitstream/1885/42030/2/hon-thesis.pdf cc #929 Fixes #1804
4 years ago
"log",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"memoffset",
"more-asserts",
"region",
"thiserror",
"wasmtime-environ",
"winapi",
]
[[package]]
name = "wasmtime-rust"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
"wasmtime",
"wasmtime-rust-macro",
"wasmtime-wasi",
]
[[package]]
name = "wasmtime-rust-macro"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
"syn",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "wasmtime-wasi"
Fixes needed for 0.19.0 (#2035) * Add some more wiggle crates to publish * Fix build of wasi-common on crates.io * Bump crates to 0.19.1 to fix crates.io build
4 years ago
version = "0.19.1"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Reimplement `wasmtime-wasi` on top of `wasmtime` (#899) * Reimplement `wasmtime-wasi` on top of `wasmtime` This commit reimplements the `wasmtime-wasi` crate on top of the `wasmtime` API crate, instead of being placed on top of the `wasmtime-*` family of internal crates. The purpose here is to continue to exercise the API as well as avoid usage of internals wherever possible and instead use the safe API as much as possible. The `wasmtime-wasi` crate's API has been updated as part of this PR as well. The general outline of it is now: * Each module snapshot has a `WasiCtxBuilder`, `WasiCtx`, and `Wasi` type. * The `WasiCtx*` types are reexported from `wasi-common`. * The `Wasi` type is synthesized by the `wig` crate's procedural macro * The `Wasi` type exposes one constructor which takes a `Store` and a `WasiCtx`, and produces a `Wasi` * Each `Wasi` struct fields for all the exported functions in that wasi module. They're all public an they all have type `wasmtime::Func` * The `Wasi` type has a `get_export` method to fetch an struct field by name. The intention here is that we can continue to make progress on #727 by integrating WASI construction into the `Instance::new` experience, but it requires everything to be part of the same system! The main oddity required by the `wasmtime-wasi` crate is that it needs access to the caller's `memory` export, if any. This is currently done with a bit of a hack and is expected to go away once interface types are more fully baked in. * Remove now no-longer-necessary APIs from `wasmtime` * rustfmt * Rename to from_abi
5 years ago
"anyhow",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"log",
"wasi-common",
"wasmtime",
"wasmtime-runtime",
wasi: switch to use wasmtime-wiggle for wiggle integration
4 years ago
"wasmtime-wiggle",
Update the `*.wast` runner to use the `wasmtime` API (#690) * Update the `*.wast` runner to use the `wasmtime` API This commit migrates the `wasmtime-wast` crate, which executes `*.wast` test suites, to use the `wasmtime` crate exclusively instead of the raw support provided by the `wasmtime-*` family of crates. The primary motivation for this change is to use `*.wast` test to test the support for interface types, but interface types is only being added in the `wasmtime` crate for now rather than all throughout the core crates. This means that without this transition it's much more difficult to write tests for wasm interface types! A secondary motivation for this is that it's testing the support we provide to users through the `wasmtime` crate, since that's the expectation of what most users would use rather than the raw `wasmtime-*` crates. * Run rustfmt * Fix the multi example * Handle v128 values in the `wasmtime` crate Ensure that we allocate 128-bit stack slots instead of 64-bit stack slots. * Update to master * Add comment
5 years ago
"wig",
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
"wiggle",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "wasmtime-wast"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"anyhow",
Update the `*.wast` runner to use the `wasmtime` API (#690) * Update the `*.wast` runner to use the `wasmtime` API This commit migrates the `wasmtime-wast` crate, which executes `*.wast` test suites, to use the `wasmtime` crate exclusively instead of the raw support provided by the `wasmtime-*` family of crates. The primary motivation for this change is to use `*.wast` test to test the support for interface types, but interface types is only being added in the `wasmtime` crate for now rather than all throughout the core crates. This means that without this transition it's much more difficult to write tests for wasm interface types! A secondary motivation for this is that it's testing the support we provide to users through the `wasmtime` crate, since that's the expectation of what most users would use rather than the raw `wasmtime-*` crates. * Run rustfmt * Fix the multi example * Handle v128 values in the `wasmtime` crate Ensure that we allocate 128-bit stack slots instead of 64-bit stack slots. * Update to master * Add comment
5 years ago
"wasmtime",
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wast 21.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
create wasmtime-wiggle crate, by copying implementation of `wig`
4 years ago
[[package]]
name = "wasmtime-wiggle"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
create wasmtime-wiggle crate, by copying implementation of `wig`
4 years ago
dependencies = [
"wasmtime",
"wasmtime-wiggle-macro",
"wiggle",
"witx",
]
[[package]]
name = "wasmtime-wiggle-macro"
Fixes needed for 0.19.0 (#2035) * Add some more wiggle crates to publish * Fix build of wasi-common on crates.io * Bump crates to 0.19.1 to fix crates.io build
4 years ago
version = "0.19.1"
create wasmtime-wiggle crate, by copying implementation of `wig`
4 years ago
dependencies = [
"proc-macro2",
"quote",
"syn",
wasmtime-wiggle-macro: adopt config system from wiggle-generate
4 years ago
"wiggle-generate",
create wasmtime-wiggle crate, by copying implementation of `wig`
4 years ago
"witx",
]
Update a number of wasmtime's dependencies (#1355) * Run `cargo update` * Use `cargo outdated` to guide some manual version bumps
5 years ago
[[package]]
name = "wast"
version = "11.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df4d67ba9266f4fcaf2e8a1afadc5e2a959e51aecc07b1ecbdf85a6ddaf08bde"
dependencies = [
"leb128",
]
Fixes for 0.15 (#1449) * Wasmtime 0.15.0 and Cranelift 0.62.0. (#1398) * Bump more ad-hoc versions. * Add build.rs to wasi-common's Cargo.toml. * Update the env var name in more places. * Remove a redundant echo.
5 years ago
[[package]]
name = "wast"
Update wasmparser and wast dependencies (#1663) Brings in updates to SIMD spec ops renumbering.
5 years ago
version = "15.0.0"
Fixes for 0.15 (#1449) * Wasmtime 0.15.0 and Cranelift 0.62.0. (#1398) * Bump more ad-hoc versions. * Add build.rs to wasi-common's Cargo.toml. * Update the env var name in more places. * Remove a redundant echo.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update wasmparser and wast dependencies (#1663) Brings in updates to SIMD spec ops renumbering.
5 years ago
checksum = "a10df5277f68adee65bba117b40235f07a4cb3d59e5ec9aa86dbee180fb1bc04"
Fixes for 0.15 (#1449) * Wasmtime 0.15.0 and Cranelift 0.62.0. (#1398) * Bump more ad-hoc versions. * Add build.rs to wasi-common's Cargo.toml. * Update the env var name in more places. * Remove a redundant echo.
5 years ago
dependencies = [
"leb128",
]
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
[[package]]
name = "wast"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
version = "21.0.0"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
checksum = "0b1844f66a2bc8526d71690104c0e78a8e59ffa1597b7245769d174ebb91deb5"
Wasmtime 0.18.0 and Cranelift 0.65.0.
4 years ago
dependencies = [
"leb128",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "wat"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
version = "1.0.22"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
checksum = "ce85d72b74242c340e9e3492cfb602652d7bb324c3172dd441b5577e39a2e18c"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Update wasmparser to 0.59.0 (#2013) This commit is intended to update wasmparser to 0.59.0. This primarily includes bytecodealliance/wasm-tools#40 which is a large update to how parsing and validation works. The impact on Wasmtime is pretty small at this time, but over time I'd like to refactor the internals here to lean more heavily on that upstream wasmparser refactoring. For now, though, the intention is to get on the train of wasmparser's latest `main` branch to ensure we get bug fixes and such. As part of this update a few other crates and such were updated. This is primarily to handle the new encoding of `ref.is_null` where the type is not part of the instruction encoding any more.
4 years ago
"wast 21.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "wig"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"heck",
Update dependencies to current versions, reducing duplicate versions (#963) * Cargo.lock: Update, to no longer use multiple versions of autocfg * Update wasmtime-debug and wasmtime-profiling to current gimli 0.20.0 This also eliminates duplicate versions of gimli and arrayvec, and eliminates the nodrop dependency entirely. * Update wasmtime-profiling to goblin 0.1.3 and object 0.17.0 This also eliminates two duplicate versions of goblin, and duplicate versions of proc-macro2, quote, syn, scroll_derive, and unicode-xid. * Update wasmtime-profiling to current scroll 0.10.1 This eliminates duplicate versions of scroll. * Update wasmtime-profiling to current target-lexicon 0.10.0 This eliminates duplicate versions of target-lexicon. * Update wasmtime-interface-types to current walrus and wasm-webidl-bindings This also eliminates the oldest of the three duplicate versions of wasmparser. * Update wasmtime-wast to current wast 8.0.0 This eliminates one of the duplicate versions of wast.
5 years ago
"proc-macro2",
"quote",
Update wasi submodule (#1345) * Update wasi submodule Removes some dependencies from the `witx` crate since WebAssembly/WASI#243 * Don't pull witx from two places * Update submodule again
5 years ago
"witx",
Fix wiggle's tests
5 years ago
]
[[package]]
name = "wiggle"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Fix wiggle's tests
5 years ago
dependencies = [
"proptest",
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
"thiserror",
use tracing 0.1.15 release
4 years ago
"tracing",
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
"wiggle-macro",
Fix wiggle's tests
5 years ago
"wiggle-test",
Update wasi submodule (#1345) * Update wasi submodule Removes some dependencies from the `witx` crate since WebAssembly/WASI#243 * Don't pull witx from two places * Update submodule again
5 years ago
"witx",
Fix wiggle's tests
5 years ago
]
[[package]]
name = "wiggle-generate"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Fix wiggle's tests
5 years ago
dependencies = [
"anyhow",
"heck",
"proc-macro2",
"quote",
"syn",
Update wasi submodule (#1345) * Update wasi submodule Removes some dependencies from the `witx` crate since WebAssembly/WASI#243 * Don't pull witx from two places * Update submodule again
5 years ago
"witx",
Fix wiggle's tests
5 years ago
]
[[package]]
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
name = "wiggle-macro"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Fix wiggle's tests
5 years ago
dependencies = [
wiggle-generate: paramaterize library on module path to runtime (#1574) * wiggle-generate: paramaterize library on module path to runtime This change makes no functional difference to users who only use the wiggle crate. Add a parameter to the `Names` constructor that determines the module that runtime components (e.g. GuestPtr, GuestError etc) of wiggle come from. For `wiggle` users this is just `quote!(wiggle)`, but other libraries which consume wiggle-generate may wrap and re-export wiggle under some other path, and not want their consumers to have to know about the wiggle dependency, e.g. `quote!(my_crate::some_path::wiggle)`. * wiggle-generate,macro: move more logic into macro better for code reuse elsewhere
5 years ago
"quote",
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
"syn",
"wiggle",
"wiggle-generate",
wiggle: emit a metadata module containing witx document (#1387) * wiggle: emit a metadata module containing witx document * wiggle: put metadata module behind a wiggle_metadata feature * wasi-common: add wiggle_metadata feature and optional witx dep * refactor according to alex's advice * wasi-common: make snapshots pub * wasi-common: i do need a wiggle_metadata feature to be available * Tweak features and such * wiggle: fix tests by passing metadata flag to wiggle-runtime * wiggle: need to move wiggle-runtime to a non-dev dependency so that the feature resolves for external users of the crates Co-authored-by: Alex Crichton <alex@alexcrichton.com>
5 years ago
"witx",
Fix wiggle's tests
5 years ago
]
[[package]]
name = "wiggle-test"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Fix wiggle's tests
5 years ago
dependencies = [
externref: Address review feedback
4 years ago
"env_logger",
Fix wiggle's tests
5 years ago
"proptest",
wiggle: can swap in `tracing` for args
5 years ago
"thiserror",
use tracing 0.1.15 release
4 years ago
"tracing",
wiggle: can swap in `tracing` for args
5 years ago
"tracing-subscriber",
Shuffle around the wiggle crates (#1414) * Shuffle around the wiggle crates This commit reorganizes the wiggle crates slightly by performing the following transforms: * The `crates/wiggle` crate, previously named `wiggle`, was moved to `crates/wiggle/crates/macro` and is renamed to `wiggle-macro`. * The `crates/wiggle/crates/runtime` crate, previously named `wiggle-runtime`, was moved to `crates/wiggle` and is renamed to `wiggle`. * The new `wiggle` crate depends on `wiggle-macro` and reexports the macro. The goal here is that consumers only deal with the `wiggle` crate itself. No more crates depend on `wiggle-runtime` and all dependencies are entirely on just the `wiggle` crate. * Remove the `crates/wiggle/crates` directory Move everything into `crates/wiggle` directly, like `wasi-common` * Add wiggle-macro to test-all script * Fixup a test
5 years ago
"wiggle",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "winapi"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.3.9"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
version = "0.1.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
Update deps and tests for `anyref` --> `externref` * Update to using `wasmparser` 0.55.0 * Update wasmprinter to 0.2.5 * Update `wat` to 1.0.18, and `wast` to 17.0.0
5 years ago
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"winapi",
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
[[package]]
name = "winx"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"bitflags",
"cvt",
"winapi",
]
[[package]]
name = "witx"
bump witx dep to 0.8.5
5 years ago
version = "0.8.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
Upgrade to witx 0.8.0 with tagged unions (#921) * witx tagged unions: updates to wig to use new semantics * wig: emit a `#variant: ()` union variant for empty variants * wasi-common: translate to use tagged unions * update to flattened layout of event struct * wig: generate layout tests, and delete bindgen ones the bindgen tests became out-of-date with the latest changes to the representation of unions, and the re-jiggering of various struct definitions that went along with it. * wasi: point at master with tagged union PR merged * fix event struct repr on windows
5 years ago
"anyhow",
"diff",
Auto-generate the `hostcalls` module of `wasi-common` (#846) * Auto-generate shims for old `wasi_unstable` module This commit is effectively just doing what #707 already did, but applying it to the `snapshot_0` module as well. The end result is the same, where we cut down on all the boilerplate in `snapshot_0` and bring it in line with the main `wasi_snapshot_preview1` implementation. The goal here is to make it easier to change the two in tandem since they're both doing the same thing. * Migrate `wasi_common::hostcalls` to a macro This commit migrates the `hostcalls` module to being auto-generated by a macro rather than duplicating a handwritten signature for each wasi syscall. * Auto-generate snapshot_0's `hostcalls` module Similar to the previous commit, but for `snapshot_0` * Delete the `wasi-common-cbindgen` crate This is no longer needed with the hostcalls macro now, we can easily fold the definition of the cbindgen macro into the same crate. * Rustfmt * Fix windows build errors * Rustfmt * Remove now no-longer-necessary code * rustfmt
5 years ago
"log",
bump witx dep to 0.8.5
5 years ago
"pretty_env_logger",
Upgrade to witx 0.8.0 with tagged unions (#921) * witx tagged unions: updates to wig to use new semantics * wig: emit a `#variant: ()` union variant for empty variants * wasi-common: translate to use tagged unions * update to flattened layout of event struct * wig: generate layout tests, and delete bindgen ones the bindgen tests became out-of-date with the latest changes to the representation of unions, and the re-jiggering of various struct definitions that went along with it. * wasi: point at master with tagged union PR merged * fix event struct repr on windows
5 years ago
"structopt",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"thiserror",
bump witx dep to 0.8.5
5 years ago
"wast 11.0.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
]
[[package]]
name = "yanix"
Wasmtime 0.19.0 and Cranelift 0.66.0 (#2027) This commit updates Wasmtime's version to 0.19.0, Cranelift's version to 0.66.0, and updates the release notes as well.
4 years ago
version = "0.19.0"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"bitflags",
"cfg-if",
[wasi-common]: move filetime module to yanix (#1255) * Move filetime module to yanix I've noticed that we could replace every occurrence of `crate::Result` in `filetime` mods with `io::Result`, so I thought why not move it to `yanix` and get rid off a lot of unnecessary code duplication within `wasi-common`. Now, ideally I'd have our `filetime` modifications backported to Alex's [`filetime`] crate, but one step at a time (apologies Alex, I was meant to backport this ages ago, just didn't find the time yet... :-(). Anyway, this commit does just that; i.e., moves the `filetime` modules into `yanix` which seems a better fit for this type of code. [`filetime`]: https://github.com/alexcrichton/filetime There is one caveat here. On Emscripten, converting between `filetime::Filetime` and `libc::timespec` appears to be lossy, at least as far as the types are concerned. Now, `filetime::Filetime`'s seconds field is `i64` while nanoseconds field is `u32`, while Emscripten's `libc::timespec` requires both to be `i32` width. This might actually not be a problem since I don't think it's possible to fill `filetime::Filetime` struct with values of width wider than `i32` since Emscripten is 32bit but just to be on the safe side, we do a `TryInto` conversion, log the error (if any), and return `libc::EOVERFLOW`. * Run cargo fmt * Use i64::from instead of as cast
5 years ago
"filetime",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"libc",
"log",
]
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
[[package]]
name = "z3"
deps: Bump `z3` to 0.6.0 Z3 is used by `peepmatic`.
4 years ago
version = "0.6.0"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: Bump `z3` to 0.6.0 Z3 is used by `peepmatic`.
4 years ago
checksum = "f0354c65dfe00e08c4ab30581732906874f97156f424bfb390cf0cca2cb6ac29"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"lazy_static",
"log",
"z3-sys",
]
[[package]]
name = "z3-sys"
deps: Bump `z3` to 0.6.0 Z3 is used by `peepmatic`.
4 years ago
version = "0.6.2"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: Bump `z3` to 0.6.0 Z3 is used by `peepmatic`.
4 years ago
checksum = "e1863cafae8eb86dd7d69c9218421b288594e8836346e93d4f36ade427195a21"
cranelift: Port most of `simple_preopt.rs` over to the `peepmatic` DSL This ports all of the identity, no-op, simplification, and canonicalization related optimizations over from being hand-coded to the `peepmatic` DSL. This does not handle the branch-to-branch optimizations or most of the divide-by-constant optimizations.
5 years ago
dependencies = [
"cmake",
]
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
[[package]]
name = "zstd"
externref: Address review feedback
4 years ago
version = "0.5.3+zstd.1.4.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "01b32eaf771efa709e8308605bbf9319bf485dc1503179ec0469b611937c0cd8"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"zstd-safe",
]
[[package]]
name = "zstd-safe"
externref: Address review feedback
4 years ago
version = "2.0.5+zstd.1.4.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "1cfb642e0d27f64729a639c52db457e0ae906e7bc6f5fe8f5c453230400f1055"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"libc",
"zstd-sys",
]
[[package]]
name = "zstd-sys"
externref: Address review feedback
4 years ago
version = "1.4.17+zstd.1.4.5"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
source = "registry+https://github.com/rust-lang/crates.io-index"
externref: Address review feedback
4 years ago
checksum = "b89249644df056b522696b1bb9e7c18c87e8ffa3e2f0dc3b0155875d6498f01b"
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
dependencies = [
"cc",
"glob",
externref: Address review feedback
4 years ago
"itertools 0.9.0",
Commit Cargo.lock. (#705) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format
5 years ago
"libc",
]