about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stdio.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-11-08 22:27:06 +0000
committerbors <bors@rust-lang.org>2017-11-08 22:27:06 +0000
commitda3fbe750fa0f971f24a41e574fd44ca582be239 (patch)
tree111002871878f519abc8135ac7846827aad49727 /src/libstd/sys/unix/stdio.rs
parent02004ef78383cb174a41df7735a552823fa10b90 (diff)
parentd01b89b94827f7d818397d8b4654e93306219ec0 (diff)
downloadrust-da3fbe750fa0f971f24a41e574fd44ca582be239.tar.gz
rust-da3fbe750fa0f971f24a41e574fd44ca582be239.zip
Auto merge of #45867 - michaelwoerister:check-ich-stability, r=nikomatsakis
incr.comp.: Verify stability of incr. comp. hashes and clean up various other things.

The main contribution of this PR is that it adds the `-Z incremental-verify-ich` functionality. Normally, when the red-green tracking system determines that a certain query result has not changed, it does not re-compute the incr. comp. hash (ICH) for that query result because that hash is already known. `-Z incremental-verify-ich` tells the compiler to re-hash the query result and compare the new hash against the cached hash. This is a rather thorough way of
- testing hashing implementation stability,
- finding missing `[input]` annotations on `DepNodes`, and
- finding missing read-edges,

since both a missed read and a missing `[input]` annotation can lead to something being marked as green instead of red and thus will have a different hash than it should have.

Case in point, implementing this verification logic and activating it for all `src/test/incremental` tests has revealed several such oversights, all of which are fixed in this PR.

r? @nikomatsakis
Diffstat (limited to 'src/libstd/sys/unix/stdio.rs')
0 files changed, 0 insertions, 0 deletions