update readme

Author: RalfJung

README.md

@@ -7,25 +7,27 @@ Every night, a Travis cron job runs the tests against the latest nightly, to mak
 To run the tests yourself, make sure you have Miri installed (`rustup component add miri`) and then run:
 
 ```shell
-./run-test.sh core
-./run-test.sh alloc
+./run-test.sh core --all-targets
+./run-test.sh alloc --all-targets
 ```
 
 This will run the test suite of the standard library of your current toolchain.
+`--all-targets` means that doc tests are skipped; those should use separate Miri flags as there are some (expected) memory leaks.
 If you are working on the standard library and want to check that the tests pass with your modifications, set `RUST_SRC` to the checkout you are working in:
 
 ```shell
-RUST_SRC=~/path/to/rustc ./run-test.sh core
+RUST_SRC=~/path/to/rustc ./run-test.sh core --all-targets
 ```
 
 Here, `~/path/to/rustc` should be the directory containing `x.py`.
 Then the test suite will be compiled from the standard library in that directory.
 Make sure that is as close to your rustup default toolchain as possible, as the toolchain will still be used to build that standard library and its test suite.
 
-`run-test` also accepts parameters that are passed to Miri and the test runner:
+`run-test` also accepts parameters that are passed to `cargo test` and the test runner,
+and `MIRIFLAGS` can be used as usual to pass parameters to Miri:
 
 ```shell
-./run-test.sh alloc -Zmiri-flags -- test-params
+MIRIFLAGS="-Zmiri-ignore-leaks -Zmiri-disable-isolation" ./run-test.sh alloc --doc -- --skip vec
 ```
 
 If you want to know how long each test took to execute, add `2>&1 | ts -m -i '%.s  '` to the end of the command.