cranelift

6091 Commits

49 Branches

140 Tags

128 MiB

Tree: 6822c9bdc1

Commit Graph

Author	SHA1	Message	Date
Alex Crichton	d5a2eb397c	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
Alex Crichton	ca36e4040d	Move the `fuzz` directory into main workspace This'll help us track dependencies and head off issues like #721	5 years ago
Dan Gohman	3e4a6510f1	Commit Cargo.lock. (#705 ) * Commit Cargo.lock. The Cargo documentation recommends packages which produce end-user programs, which wasmtime-cli is, to check in their Cargo.lock files: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries * Use Cargo's newer less-conflicting lockfile format	5 years ago

Author

SHA1

Message

Date

Alex Crichton

d5a2eb397c

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

Alex Crichton

ca36e4040d

Move the `fuzz` directory into main workspace

This'll help us track dependencies and head off issues like #721

5 years ago

Dan Gohman

3e4a6510f1

Commit Cargo.lock. (#705 )

* Commit Cargo.lock.

The Cargo documentation recommends packages which produce end-user
programs, which wasmtime-cli is, to check in their Cargo.lock files:

https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries

* Use Cargo's newer less-conflicting lockfile format

5 years ago

106 Commits (6822c9bdc18e543be540b4b656602ff5cd6b875c)