en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#703871a2 Enable the `useless_conversion` Clippy lint (#10838)* Enable the `useless_conversion` Clippy lintWe've got lots of types in Wasmtime and convert between them quite alot, but often over time conversions become unnecessary throughrefactorings or similar. This will hopefully enable us to clean up someconversions as they come up to try to have as few as possible ideally.* Review comments List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Tue, 27 May 2025 16:49:22 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#90ac295e Update Wasmtime to the 2024 Rust Edition (#10806)* Update Wasmtime to the 2024 Rust EditionNow that our MSRV supports the 2024 edition it's possible to make thisswitch. This commit moves Wasmtime to the 2024 Edition to keepup-to-date with Rust idioms and access many of the edition featuresexclusive to the 2024 edition.prtest:full* Reformat with the 2024 edition List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Mon, 19 May 2025 16:40:55 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#c3aa6a53 Change `allow(missing_docs)` to `expect(..)` (#10384)This wasn't possible when `expect` was first introduced due to a changebeing required in upstream rust-lang/rust. That changerust-lang/rust#130025) has now rode enough trains to be in our MSRV, sowe can expect missing docs now instead of just allowing it. List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Wed, 12 Mar 2025 18:58:45 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#71cb94be Burn down the `allow_attributes_without_reason` backlog (#9712)* Burn down the `allow_attributes_without_reason` backlogJust a bit, not everything fixed.* Fix wasi-nn annotations* Tweak `#[cfg]` List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Tue, 03 Dec 2024 16:57:45 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#a0442ea0 Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Mon, 05 Aug 2024 09:59:59 +0000 Hamir Mahal <hamirmahal@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#7e45cff4 cranelift: Bitwise compare fuzzgen results (#4855) List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Fri, 02 Sep 2022 19:34:16 +0000 Afonso Bordado <afonso360@users.noreply.github.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#f30a7eb0 cranelift: Implement PartialEq on Ieee{32,64} (#4849)* cranelift: Add `fcmp` tests Some of these are disabled on aarch64 due to not being implemented yet. * cranelift: Implement float PartialEq for Ieee{32,64} (fixes #4828) Previously `PartialEq` was auto derived. This means that it was implemented in terms of PartialEq in a u32. This is not correct for floats because `NaN != NaN`. PartialOrd was manually implemented in 6d50099816f397c1ff3256d30f742cf041d54e32, but it seems like it was an oversight to leave PartialEq out until now. The test suite depends on the previous behaviour so we adjust it to keep comparing bits instead of floats. * cranelift: Disable `fcmp ord` tests on aarch64 * cranelift: Disable `fcmp ueq` tests on aarch64 List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Fri, 02 Sep 2022 17:42:42 +0000 Afonso Bordado <afonso360@users.noreply.github.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#6f6f79ef refactor: move DataValue from cranelift-reader to cranelift-codegenThis is no change to functionality; the move is necessary in order to return InstructionData immediates in a structure way (see next commit). List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Thu, 01 Oct 2020 15:55:12 +0000 Andrew Brown <andrew.brown@intel.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#85ffc8f5 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 List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Mon, 13 Jul 2020 23:40:47 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#b4238229 Cast DataValues to and from native typesAlso, returns a `Result` in the `RunCommand::run` helper. List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Tue, 21 Apr 2020 18:53:50 +0000 Andrew Brown <andrew.brown@intel.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#d6796d0d Improve documentation of the filetest `run` command (#1645)* Improve output display of RunCommand The previous use of Debug for displaying `print` and `run` results was less than clear. * Avoid checking the types of vectors during trampoline construction Because DataValue only understands `V128` vectors, we avoid type-checking vector values when constructing the trampoline arguments. * Improve the documentation of the filetest `run` command Adds an up-to-date example of how to use the `run` and `print` directives and includes an actual use of the new directives in a SIMD arithmetic filetest. List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Mon, 04 May 2020 19:08:27 +0000 Andrew Brown <andrew.brown@intel.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#38dff291 Add ability to call CLIF functions with arbitrary arguments in filetestsThis 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 stdoutTo 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`. List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Wed, 15 Apr 2020 20:50:51 +0000 Andrew Brown <andrew.brown@intel.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#c9a0ba81 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 List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Tue, 21 Apr 2020 18:03:28 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/cranelift/reader/src/run_command.rs#50804210 Add structures to represent run commands like `run: %fn0(42, 4.2) == false` List of files: /wasmtime-44.0.1/cranelift/reader/src/run_command.rs Mon, 30 Mar 2020 19:26:34 +0000 Andrew Brown <andrew.brown@intel.com>