-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo-miri: never invoke rustc #1406
Conversation
I confirmed that rustc bootstrap still works with this PR. |
📌 Commit 12114c5 has been approved by |
cargo-miri: never invoke rustc Always go through 'MIRI_BE_RUSTC=1 miri' instead. This is based on @oli-obk's great idea to add a way to make Miri behave like rustc, which already helped us in #1405. Now it means in `cargo-miri` we run *all* crates through the same binary, and use the env var to determine if we compile or interpret them. This makes sure the compiler is consistent. The `rustc` binary of the current toolchain is now not used at all, only the `miri` binary is. In particular this means we can kill the sysroot consistency check. :)
…lready uses these flags
Oh and we also do not need to pass |
@bors retry r+ |
📌 Commit 845b89c has been approved by |
☀️ Test successful - checks-travis, status-appveyor |
Always go through 'MIRI_BE_RUSTC=1 miri' instead. This is based on @oli-obk's great idea to add a way to make Miri behave like rustc, which already helped us in #1405. Now it means in
cargo-miri
we run all crates through the same binary, and use the env var to determine if we compile or interpret them. This makes sure the compiler is consistent.The
rustc
binary of the current toolchain is now not used at all, only themiri
binary is. In particular this means we can kill the sysroot consistency check. :)