Go to file
2017-07-03 20:37:38 -07:00
benches Rustup to rustc 1.19.0-nightly (2d4ed8e0c 2017-05-03) 2017-05-04 17:42:43 +02:00
cargo-miri-test add a dependency to cargo-miri-test 2017-06-29 14:00:24 -04:00
src check the assumptions made by the unchecked_ and copy_nonoverlapping intrinsics 2017-07-03 20:37:38 -07:00
tests check the assumptions made by the unchecked_ and copy_nonoverlapping intrinsics 2017-07-03 20:37:38 -07:00
tex fix tuple example in slides 2016-05-14 15:13:06 +10:00
xargo add instructions for how to compile libstd with xargo 2017-05-30 10:41:38 -07:00
.editorconfig Add EditorConfig 2016-04-14 14:54:59 +02:00
.gitignore add tests for cargo miri and run them on travis 2017-01-28 11:57:53 +01:00
.travis.yml Add fullmir tests 2017-06-21 08:57:17 +02:00
Cargo.lock update compiletest dependency 2017-06-30 12:06:49 -04:00
Cargo.toml Update dependencies 2017-05-09 16:47:04 +02:00
LICENSE-APACHE Add licenses and readme. 2016-02-02 04:47:28 -06:00
LICENSE-MIT Add licenses and readme. 2016-02-02 04:47:28 -06:00
README.md update xargo usage example for new location of vecs.rs 2017-06-22 17:44:20 +09:00

Miri [slides] [report] Build Status

An experimental interpreter for Rust's mid-level intermediate representation (MIR). This project began as part of my work for the undergraduate research course at the University of Saskatchewan.

Installing Rust

I recommend that you install rustup and then use it to install the current Rust nightly version:

rustup update nightly

You should also make nightly the default version for your Miri directory by running the following command while you're in it. If you don't do this, you can run the later cargo commands by using cargo +nightly instead.

rustup override add nightly

Building Miri

cargo build

If Miri fails to build, it's likely because a change in the latest nightly compiler broke it. You could try an older nightly with rustup update nightly-<date> where <date> is a few days or weeks ago, e.g. 2016-05-20 for May 20th. Otherwise, you could notify me in an issue or on IRC. Or, if you know how to fix it, you could send a PR. 😄

Running tests

cargo run --bin miri tests/run-pass/vecs.rs # Or whatever test you like.

Debugging

You can get detailed, statement-by-statement traces by setting the MIRI_LOG environment variable to trace. These traces are indented based on call stack depth. You can get a much less verbose set of information with other logging levels such as warn.

Running miri on your own project('s test suite)

Install miri as a cargo subcommand with cargo install --debug. Then, inside your own project, use cargo +nightly miri to run your project, if it is a bin project, or run cargo +nightly miri test to run all tests in your project through miri.

Running miri with full libstd

Per default libstd does not contain the MIR of non-polymorphic functions. When miri hits a call to such a function, execution terminates. To fix this, it is possible to compile libstd with full MIR:

rustup component add rust-src
cargo install xargo
cd xargo/
RUSTFLAGS='-Zalways-encode-mir' xargo build

Now you can run miri against the libstd compiled by xargo:

MIRI_SYSROOT=~/.xargo/HOST cargo run --bin miri tests/run-pass-fullmir/vecs.rs

Notice that you will have to re-run the last step of the preparations above when your toolchain changes (e.g., when you update the nightly).

Contributing and getting help

Check out the issues on this GitHub repository for some ideas. There's lots that needs to be done that I haven't documented in the issues yet, however. For more ideas or help with running or hacking on Miri, you can contact me (scott) on Mozilla IRC in any of the Rust IRC channels (#rust, #rust-offtopic, etc).

License

Licensed under either of

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.