Go to file
2016-09-23 10:38:30 +02:00
benches Run Mir passes (copied from rustc pre-trans). 2016-06-30 21:33:24 -06:00
src implement "type_name" intrinsic 2016-09-23 10:38:30 +02:00
tests refactor away intermediate allocations, stage1 2016-09-23 10:27:14 +02:00
tex fix tuple example in slides 2016-05-14 15:13:06 +10:00
.editorconfig Add EditorConfig 2016-04-14 14:54:59 +02:00
.gitignore Move slides into new tex directory. 2016-04-08 13:25:36 -06:00
.travis.yml miri needs to be *built* with RUST_SYSROOT, not *run* 2016-06-16 11:00:46 +02:00
Cargo.lock rustup to rustc 1.13.0-nightly (91f057de3 2016-09-04) 2016-09-06 16:04:51 +02:00
Cargo.toml create a miri-pass test that allows us to run miri for arbitrary targets 2016-06-15 16:01:00 +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 Remove stray backquote. 2016-06-19 00:15:03 -06: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 prefixing them with rustup run nightly.

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 tests/run-pass/vecs.rs # Or whatever test you like.

Debugging

You can get detailed, statement-by-statement traces by setting the MIRI_RUN 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.

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.