Skip to content

Verify correct number and types of arguments enter wasm#890

Merged
alexcrichton merged 1 commit intobytecodealliance:masterfrom
alexcrichton:check-types
Feb 4, 2020
Merged

Verify correct number and types of arguments enter wasm#890
alexcrichton merged 1 commit intobytecodealliance:masterfrom
alexcrichton:check-types

Conversation

@alexcrichton
Copy link
Member

Whenever we enter wasm code we need to verify that the correct number
and the correct types of arguments were passed in, lest we misinterpret
bits!

Closes #52

Whenever we enter wasm code we need to verify that the correct number
and the correct types of arguments were passed in, lest we misinterpret
bits!

Closes #52
@alexcrichton alexcrichton merged commit 76f9e7e into bytecodealliance:master Feb 4, 2020
@alexcrichton alexcrichton deleted the check-types branch February 4, 2020 15:13
arkpar pushed a commit to paritytech/wasmtime that referenced this pull request Mar 4, 2020
…dealliance#890)

* Add ability to run CLIF IR using `clif-util run [-v] {file}` and add `test run` to cranelift-filetests to allow executing CLIF

This re-factors the compile/execute parts to a FunctionRunner that is shared between cranelift-filetests and clif-util. CLIF can be now be run using `clif-util run` as well as during `clif-util test` for files with a `test run` header. As before, only functions suffixed with a `run` comment are executed. The `run: fn(...) == ...` expression syntax is left for a subsequent change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

invoke doesn't check that the right number of arguments are passed

2 participants