From: Oli Scherer Date: Sat, 30 Jan 2021 19:06:05 +0000 (+0100) Subject: Update README.md X-Git-Url: https://git.lizzy.rs/?a=commitdiff_plain;h=397443093de127ada63ec74bd048394050aa1a10;p=rust.git Update README.md --- diff --git a/README.md b/README.md index d742d7558c4..ae70c80d5f0 100644 --- a/README.md +++ b/README.md @@ -195,6 +195,10 @@ up the sysroot. If you are using `miri` (the Miri driver) directly, see the Miri adds its own set of `-Z` flags, which are usually set via the `MIRIFLAGS` environment variable: +* `-Zmiri-compare-exchange-weak-failure-rate=` changes the failure rate of + `compare_exchange_weak` operations. The default is `0.8` (so 4 out of 5 weak ops will fail). + You can change it to any value between `0.0` and `1.0`, where `1.0` means it + will always fail and `0.0` means it will never fail. * `-Zmiri-disable-alignment-check` disables checking pointer alignment, so you can focus on other failures, but it means Miri can miss bugs in your program. Using this flag is **unsound**. @@ -251,10 +255,6 @@ environment variable: can recognize false positives by "" occurring in the message -- this indicates a pointer that was cast from an integer, so Miri was unable to track this pointer. -* `-Zmiri-compare-exchange-weak-failure-rate=` changes the failure rate of - `compare_exchange_weak` operations. The default is `0.8` (so 4 out of 5 weak ops will fail). - You can change it to any value between `0.0` and `1.0`, where `1.0` means it - will always fail and `0.0` means it will never fail. Some native rustc `-Z` flags are also very relevant for Miri: