From 34f64cddf54595bd3a64418b038ce0d593458b30 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Tue, 7 May 2024 20:33:18 +0200 Subject: [PATCH] remove problems that I do not think we have seen in a while --- src/tools/miri/README.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/src/tools/miri/README.md b/src/tools/miri/README.md index 3b2f3ea34f4e..2c76749fbca1 100644 --- a/src/tools/miri/README.md +++ b/src/tools/miri/README.md @@ -265,25 +265,12 @@ To get a backtrace, you need to disable isolation RUST_BACKTRACE=1 MIRIFLAGS="-Zmiri-disable-isolation" cargo miri test ``` -#### "found possibly newer version of crate `std` which `` depends on" - -Your build directory may contain artifacts from an earlier build that have/have -not been built for Miri. Run `cargo clean` before switching from non-Miri to -Miri builds and vice-versa. - #### "found crate `std` compiled by an incompatible version of rustc" You may be running `cargo miri` with a different compiler version than the one used to build the custom libstd that Miri uses, and Miri failed to detect that. Try running `cargo miri clean`. -#### "no mir for `std::rt::lang_start_internal`" - -This means the sysroot you are using was not compiled with Miri in mind. This -should never happen when you use `cargo miri` because that takes care of setting -up the sysroot. If you are using `miri` (the Miri driver) directly, see the -[contributors' guide](CONTRIBUTING.md) for how to use `./miri` to best do that. - ## Miri `-Z` flags and environment variables [miri-flags]: #miri--z-flags-and-environment-variables