`MIRI_LOG` environment variable. For example:
```sh
-MIRI_LOG=info ./miri run tests/run-pass/vecs.rs
+MIRI_LOG=info ./miri run tests/run-pass/vec.rs
```
Setting `MIRI_LOG` like this will configure logging for Miri itself as well as
stacked borrows implementation:
```sh
-MIRI_LOG=rustc_mir::interpret=info,miri::stacked_borrows ./miri run tests/run-pass/vecs.rs
+MIRI_LOG=rustc_mir::interpret=info,miri::stacked_borrows ./miri run tests/run-pass/vec.rs
```
In addition, you can set `MIRI_BACKTRACE=1` to get a backtrace of where an
# Clone the rust-lang/rust repo.
git clone https://github.com/rust-lang/rust rustc
cd rustc
-cp config.toml.example config.toml
-# Now edit `config.toml` and set `debug-assertions = true`.
+# Create a config.toml with defaults for working on miri.
+./x.py setup compiler
+ # Now edit `config.toml` and under `[rust]` set `debug-assertions = true`.
-# Build a stage 1 rustc.
+# Build a stage 1 rustc, and build the rustc libraries with that rustc.
# This step can take 30 minutes or more.
./x.py build --stage 1 compiler/rustc
# If you change something, you can get a faster rebuild by doing
rustup override set stage1
```
+For more information about building and configuring a local compiler,
+see <https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html>.
+
With this, you should now have a working development setup! See
[above](#building-and-testing-miri) for how to proceed working on Miri.