about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2025-07-12 08:55:17 +0200
committerRalf Jung <post@ralfj.de>2025-07-12 08:55:17 +0200
commitbccc32bf791d7a0f5ccb0f345223548b9ae98844 (patch)
treebd190fb38e6efc3e599d7c6604ef5322df0bb014
parent317f59dfebb3ca584c4ab7c137208bbb23601eb2 (diff)
downloadrust-bccc32bf791d7a0f5ccb0f345223548b9ae98844.tar.gz
rust-bccc32bf791d7a0f5ccb0f345223548b9ae98844.zip
readme: update strict provenance link
-rw-r--r--src/tools/miri/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/tools/miri/README.md b/src/tools/miri/README.md
index b05acff72b5..7816ce1ac56 100644
--- a/src/tools/miri/README.md
+++ b/src/tools/miri/README.md
@@ -342,9 +342,9 @@ environment variable. We first document the most relevant and most commonly used
   is enabled (the default), this is also used to emulate system entropy. The default seed is 0. You
   can increase test coverage by running Miri multiple times with different seeds.
 * `-Zmiri-strict-provenance` enables [strict
-  provenance](https://github.com/rust-lang/rust/issues/95228) checking in Miri. This means that
-  casting an integer to a pointer will stop execution because the provenance of the pointer
-  cannot be determined.
+  provenance](https://doc.rust-lang.org/nightly/std/ptr/index.html#strict-provenance) checking in
+  Miri. This means that casting an integer to a pointer will stop execution because the provenance
+  of the pointer cannot be determined.
 * `-Zmiri-symbolic-alignment-check` makes the alignment check more strict.  By default, alignment is
   checked by casting the pointer to an integer, and making sure that is a multiple of the alignment.
   This can lead to cases where a program passes the alignment check by pure chance, because things