@@ -324,10 +324,6 @@ environment variable. We first document the most relevant and most commonly used
324
324
ensure alignment. (The standard library `align_to` method works fine in both modes; under
325
325
symbolic alignment it only fills the middle slice when the allocation guarantees sufficient
326
326
alignment.)
327
- * `-Zmiri-tag-gc=<blocks>` configures how often the pointer tag garbage collector runs. The default
328
- is to search for and remove unreachable tags once every `10,000` basic blocks. Setting this to
329
- ` 0` disables the garbage collector, which causes some programs to have explosive memory usage
330
- and/or super-linear runtime.
331
327
332
328
The remaining flags are for advanced use only, and more likely to change or be removed.
333
329
Some of these are **unsound**, which means they can lead
@@ -378,6 +374,10 @@ to Miri failing to detect cases of undefined behavior in a program.
378
374
* `-Zmiri-retag-fields` changes Stacked Borrows retagging to recurse into fields.
379
375
This means that references in fields of structs/enums/tuples/arrays/... are retagged,
380
376
and in particular, they are protected when passed as function arguments.
377
+ * `-Zmiri-tag-gc=<blocks>` configures how often the pointer tag garbage collector runs. The default
378
+ is to search for and remove unreachable tags once every `10000` basic blocks. Setting this to
379
+ ` 0` disables the garbage collector, which causes some programs to have explosive memory usage
380
+ and/or super-linear runtime.
381
381
* `-Zmiri-track-alloc-id=<id1>,<id2>,...` shows a backtrace when the given allocations are
382
382
being allocated or freed. This helps in debugging memory leaks and
383
383
use after free bugs. Specifying this argument multiple times does not overwrite the previous
0 commit comments