Mark incremental-ignore-spans as TRACKED.
Using that options basically changes all stable hashes we may compute. Adding/removing as UNTRACKED it makes everything ICE (unstable fingerprint everywhere). As TRACKED, it can still do its job without ICEing.
This commit is contained in:
parent
6d42636456
commit
44972b2ce7
2 changed files with 2 additions and 2 deletions
|
@ -1333,7 +1333,7 @@ options! {
|
|||
"generate human-readable, predictable names for codegen units (default: no)"),
|
||||
identify_regions: bool = (false, parse_bool, [UNTRACKED],
|
||||
"display unnamed regions as `'<id>`, using a non-ident unique id (default: no)"),
|
||||
incremental_ignore_spans: bool = (false, parse_bool, [UNTRACKED],
|
||||
incremental_ignore_spans: bool = (false, parse_bool, [TRACKED],
|
||||
"ignore spans during ICH computation -- used for testing (default: no)"),
|
||||
incremental_info: bool = (false, parse_bool, [UNTRACKED],
|
||||
"print high-level information about incremental reuse (or the lack thereof) \
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue