diff options
| author | bors <bors@rust-lang.org> | 2024-04-15 14:42:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-15 14:42:33 +0000 |
| commit | 69e8e2d800705e572653e166e6e1c58566759b66 (patch) | |
| tree | 8144345087d80133f0b80571cb6fb392a5287201 /compiler/rustc_pattern_analysis/src/errors.rs | |
| parent | 34ab66857e35a6045108519a3c37125e3c581371 (diff) | |
| parent | 9ec38eafc907969c1140bedab06874c2628b38dd (diff) | |
| download | rust-69e8e2d800705e572653e166e6e1c58566759b66.tar.gz rust-69e8e2d800705e572653e166e6e1c58566759b66.zip | |
Auto merge of #3411 - RalfJung:sysroot, r=RalfJung
Handle Miri sysroot entirely outside the Miri driver (Extracted from https://github.com/rust-lang/miri/pull/3409) This entirely moves the responsibility of setting miri-sysroot to whatever *invokes* the Miri driver. cargo-miri knows whether it is inside rustdoc or not and can adjust accordingly. I previously avoided doing that because there are a bunch of places that are invoking the driver (cargo-miri, the ui test suite, `./miri run`, `./x.py run miri`) and they all need to be adjusted now. But it is also somewhat less fragile as we usually have more information there -- and we can just decide that `./miri run file.rs --sysroot path` is not supported. The advantage of this is that the driver is reasonably clean and doesn't need magic environment variables like MIRI_SYSROOT, and we don't have to fight rustc_driver to use a different default sysroot. Everything is done in cargo-miri (and the other much simpler driver wrappers) where it can hopefully be debugged much better.
Diffstat (limited to 'compiler/rustc_pattern_analysis/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
