Commit Graph

11 Commits

Author SHA1 Message Date
DavidKorczynski 2c164afcba
wasmtime: migrate build to work with CIFUzz (#6923) 2021-11-29 19:26:51 +00:00
jonathanmetzman b15c167739
[infra][rust] Split out rust projects to their own builder image (#6352) 2021-08-30 11:47:04 -07:00
Andrew Brown face127c59
wasmtime: install a newer version of OCaml (#6205)
* wasmtime: install a newer version of OCaml

* Update Dockerfile

* wasmtime: move environment setup to build.sh
2021-08-12 09:38:22 +01:00
Andrew Brown d63a5f1432
wasmtime: provide OCaml packages for build (#6193)
* wasmtime: provide OCaml packages for build

In order to build the WebAssembly spec interpreter, these packages are needed.

* wasmtime: remove ocamlbuild as a dependency

The oss-fuzz-base image is using Ubuntu 16.04.7 and the `ocaml-nox` package at this version contains `ocamlbuild`.
2021-08-10 22:30:39 +00:00
Chris Fallin 5fdc24206e
wasmtime: add register allocator to fuzz targets. (#4669)
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.
2020-11-20 07:37:16 -08:00
Alex Crichton cd665e2a82
Add wasm-tools repository to wasmtime project (#4111)
* 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
2020-07-10 19:25:01 -07:00
devtty1er d561c49ae5
Update Dockerfiles (#4070)
* Use LABEL in place of MAINTAINER

* Remove LABEL maintainer from Dockerfiles
2020-07-06 13:18:23 -07:00
Abhishek Arya 4f7cf1b334
Simplify rust project setup. (#3830)
* 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.
2020-05-17 16:45:54 -07:00
Alex Crichton 94d0c3a7b4
[wasmtime] Try fixing delivery of SIGILL/SIGSEGV to JIT (#3335)
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.
2020-02-05 09:46:23 -08:00
Alex Crichton 96c9cd26c2 Try to fix the wasmtime Rust build (#3298)
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.
2020-01-28 06:41:49 -08:00
Jonathan Foote 038d4ac14a [wasmtime] initial integration (#3292) 2020-01-27 06:40:46 -08:00