e7bcf35f8a
This takes the `AllocId` out of PrimValKind, replacing it with a `relocation` field on `PrimVal`, which is closer to an earlier design for `PrimVal` I discussed with @eddyb. This commit prepares the code for removing the `PrimValKind` from `PrimVal` and making them more pure bitbags. The only code dealing with `PrimValKind` will be code making decisions like "what kind of operation do I need to do on these bits", like operators and casting. Transmutes of `PrimVal`s will become true no-ops, not even adjusting a `kind` field. This commit also removes my horrible `value_to_primval` hack that made an allocation for every `ByVal` passed in, so it could use `read_value` to get a `PrimVal` with the right kind. Now I just compute the `PrimValKind` from the `Ty` and re-tag the `PrimVal`. The code got slightly messier in some areas here, but I think a _lot_ of code will simplify in obvious ways once I remove the `kind` field from `PrimVal`. Gosh, if my commit messages aren't turning into essays these days.
Miri [slides] [report] 
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
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT) at your option.
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.