From 03be4138ed134370979aec04ff5fe23cab6bcf74 Mon Sep 17 00:00:00 2001 From: Johnathan Van Why Date: Mon, 22 Mar 2021 15:35:18 -0700 Subject: [PATCH] `-Zmiri-track-raw-pointers` doc correction: it is not strictly more restrictive than Stacked Borrows. This change is based on the following comment: https://github.com/rust-lang/miri/pull/1748#issuecomment-803279473 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 59f7b970546e..5e5b82b36547 100644 --- a/README.md +++ b/README.md @@ -254,8 +254,9 @@ environment variable: help identify latent aliasing issues in code that Miri accepts by default. You 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. It does not have false negatives; code that works with - `-Zmiri-track-raw-pointers` will work without `-Zmiri-track-raw-pointers`. + this pointer. Note that it is not currently guaranteed that code that works + with `-Zmiri-track-raw-pointers` also works without + `-Zmiri-track-raw-pointers`. Some native rustc `-Z` flags are also very relevant for Miri: