-
Notifications
You must be signed in to change notification settings - Fork 332
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
Don't use MIRI_DEFAULT_ARGS
to compile host crates
#1761
Conversation
https://github.com/rust-lang/miri/runs/2289905504 🤔 |
That looks like a strange timer issue... I don't think it's related to this PR though. |
It somehow managed to trigger this line Line 714 in 7b2e325
That... should not be possible? We have some non-determinism somewhere... |
This is great, thanks a lot. :-) |
Squashed. 🚀 |
@bors r+ |
📌 Commit 3dff1d4 has been approved by |
☀️ Test successful - checks-actions |
update Miri Let's ship rust-lang/miri#1761. Cc `@rust-lang/miri` r? `@ghost`
They (specifically,
--cfg=miri
) may cause procedural macros (and probably build scripts) to depend on Miri-only symbols, such asmiri_resolve_frame
.This PR makes
miri
detect host crates inspecting the value of theMIRI_BE_RUSTC
environment variable (target
-> target crate,host
-> host crate, other -> panic) and skip the insertion ofMIRI_DEFAULT_ARGS
if it's a host crate.Fixes #1760