You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// always applied. However, buggy build scripts (https://github.com/eyre-rs/eyre/issues/84) and
201
199
// also cargo (https://github.com/rust-lang/cargo/issues/10885) will invoke `rustc` even when
202
200
// `RUSTC_WRAPPER` is set, bypassing the wrapper. To make sure everything is coherent, we want
203
-
// that to be the Miri driver, but acting as rustc, on the target level. (Target, rather than
204
-
// host, is needed for cross-interpretation situations.) This is not a perfect emulation of real
205
-
// rustc (it might be unable to produce binaries since the sysroot is check-only), but it's as
206
-
// close as we can get, and it's good enough for autocfg.
201
+
// that to be the Miri driver, but acting as rustc, in host mode.
207
202
//
208
203
// In `main`, we need the value of `RUSTC` to distinguish RUSTC_WRAPPER invocations from rustdoc
209
204
// or TARGET_RUNNER invocations, so we canonicalize it here to make it exceedingly unlikely that
0 commit comments