aboutsummaryrefslogtreecommitdiffhomepage
path: root/projects/wasmtime/Dockerfile
Commit message (Collapse)AuthorAge
* wasmtime: add register allocator to fuzz targets. (#4669)Gravatar Chris Fallin2020-11-20
| | | | | | | | | | | | Wasmtime uses [regalloc.rs](https://github.com/bytecodealliance/regalloc.rs), a register allocator written in Rust that was developed for use in Cranelift (but is also an independently-usable crate). While it will be indirectly fuzzed by wasmtime itself once we start fuzzing the new backends that use it, we should also fuzz it directly, since it exposes targets just for this. The regalloc fuzzing makes use of a symbolic checker as an oracle for allocation results, so should be relatively high-quality. This PR enables the `bt` (backtracking) allocator's fuzz target, as this is the default allocator.
* Add wasm-tools repository to wasmtime project (#4111)Gravatar Alex Crichton2020-07-10
| | | | | | | | | | | | * Add wasm-tools repository to wasmtime project This commit expands the fuzzers run under the Wasmtime project to include those in the https://github.com/bytecodealliance/wasm-tools repository. This includes various parsing for utilities used by Wasmtime itself but also generally useful for other Rust projects! The maintainers of the wasm-tools repository are also all currently all on the notification list for Wasmtime fuzz bugs as well. * Load all corpuses from wasmtime-libfuzzer-corpus
* Update Dockerfiles (#4070)Gravatar devtty1er2020-07-06
| | | | | * Use LABEL in place of MAINTAINER * Remove LABEL maintainer from Dockerfiles
* Simplify rust project setup. (#3830)Gravatar Abhishek Arya2020-05-17
| | | | | | | | * Simplify rust project setup. - Add rust and cargo-fuzz in base builder. - Set RUSTC_BOOSTRAP to make ASan available. - Set RUSTFLAGS and C,CXXFLAGS properly.
* [wasmtime] Try fixing delivery of SIGILL/SIGSEGV to JIT (#3335)Gravatar Alex Crichton2020-02-05
| | | | | | | This is an attempt to apply the suggestions from #3316 to the fuzzing infrastructure for the `wasmtime` target. This will hopefully allow the delivery of SIGSEGV and SIGILL signals to the `wasmtime` program itself. These are expected signals when executing wasm code so we don't want the fuzzer to treat all forms of the signal as a fatal error.
* Try to fix the wasmtime Rust build (#3298)Gravatar Alex Crichton2020-01-28
| | | | | | This is an attempt to fixup the errors found on #3292. Although I'm not certain where the error was coming from this switches the Rust installation to being in `PATH` by default so there's no need to `source` any scripts to get access to the Rust compiler.
* [wasmtime] initial integration (#3292)Gravatar Jonathan Foote2020-01-27