about summary refs log tree commit diff
path: root/src/test/incremental/hashes
AgeCommit message (Collapse)AuthorLines
2019-04-22Remove double trailing newlinesvarkor-1/+0
2019-03-30Update testsJohn Kåre Alsaker-103/+103
2019-03-20Add no_hash to query macro and move some queries overJohn Kåre Alsaker-155/+155
2019-03-18Add load_cached query modifier and keep dep node names consistent with query ↵John Kåre Alsaker-175/+175
names
2019-03-18Define queries using a proc macroJohn Kåre Alsaker-77/+77
2019-02-08Allow a dirty MirBuilt for make_extern and make_method_externJohn Kåre Alsaker-2/+2
2019-02-08Update testsJohn Kåre Alsaker-153/+153
2018-12-30Fix unresolved inference variable ICE.David Wood-1/+1
This commit moves well-formedness check for the `UserTypeAnnotation::Ty(..)` case from always running to only when the code is reachable. This solves the ICE that resulted from `src/test/ui/issue-54943-1.rs` (a minimal repro of `dropck-eyepatch` run-pass tests that failed). The main well-formedness check that was intended to be run despite unreachable code still is, that being the `UserTypeAnnotation::TypeOf(..)` case. Before this PR, the other case wasn't being checked at all. It is possible to fix this ICE while still always checking well-formedness for the `UserTypeAnnotation::Ty(..)` case but that solution will ICE in unreachable code for that case, the diff for that change [can be found here](0). [0]: https://gist.github.com/davidtwco/f9751ffd9c0508f7251c0f17adc3af53
2018-12-25Remove licensesMark Rousskov-284/+0
2018-12-07Various minor/cosmetic improvements to codeAlexander Regueiro-2/+2
2018-10-26Fix tests and assertions; add some commentsNick Cameron-1/+1
2018-10-22fix incremental testNiko Matsakis-1/+1
2018-10-02Improve implicit self mutability suggestions.David Wood-1/+1
This commit adds an `ImplicitSelfKind` to the HIR and the MIR that keeps track of whether a implicit self argument is immutable by-value, mutable by-value, immutable reference or mutable reference so that the addition of the `mut` keyword can be suggested for the immutable by-value case.
2018-09-10fix incremental testNiko Matsakis-1/+1
We are now carrying the user-given type through MIR, so it makes sense that this would change the hash.
2018-06-07Add existential type definitonsOliver Schneider-1/+1
2018-04-13Rename must-compile-successfully into compile-passGuillaume Gomez-26/+26
2018-03-26Stabilize conservative_impl_traitTaylor Cramer-1/+0
2018-03-23Fixed issues with incremental tests.David Wood-1/+1
2018-03-15Stabilize `inclusive_range_syntax` language feature.kennytm-1/+0
Stabilize the syntax `a..=b` and `..=b`.
2018-02-20rustc_mir: always run the deaggregator.Eduard-Mihai Burtescu-1/+1
2018-02-07Fix tests for MIR loop loweringbobtwinkles-1/+1
Fixes the hash test to recognize that MirValidated can change when changing around labels, and add a new test that makes sure we're lowering loop statements correctly.
2018-01-29tests: replace "lvalue" terminology with "place".Eduard-Mihai Burtescu-3/+3
2017-12-30Remove excessive trailing newlines.kennytm-5/+0
2017-12-08incr.comp.: Hash spans unconditionally for full accuracy.Michael Woerister-343/+97
2017-12-05Format function interface fingerprint hash testsJeff Crocker-56/+70
2017-12-05Update 'while loop' fingerprint hash testsJeff Crocker-54/+36
2017-12-05Update 'while let loop' fingerprint hash testsJeff Crocker-54/+36
2017-12-05Update loop expression fingerprint hash testsJeff Crocker-48/+32
2017-12-05Update inline asm fingerprint hash testsJeff Crocker-36/+24
2017-12-05Update function interface fingerprint hash testsJeff Crocker-108/+108
2017-12-05Update for loop fingerprint hash testsJeff Crocker-66/+44
2017-12-05Update closure expression fingerprint hash testsJeff Crocker-36/+24
2017-11-29incr.comp.: Update test cases after metadata hashing removal.Michael Woerister-1081/+4
2017-11-22modify inherent impls test to indicate `TypeckTables` do not changeNiko Matsakis-4/+40
I also added some comments explaining what is going on. In short, the changes in question do not, in fact, affect the`TypeckTables` in any semantic way. However, altering the order of lowering can cause it appear to affect the `TypeckTables`: if we lower generics before the body, then the `HirId` for things in the body will be affected. In this case, we are now lowering the generics etc *after* the body, so the hash no longer changes. This seems good.
2017-11-22Rollup merge of #45987 - gaurikholkar:let-expr, r=michaelwoeristerkennytm-210/+36
update let-expressions hash test to use `except` A part of #44924, this PR updated let-expressions test using `except`. cc @michaelwoerister r? @nikomatsakis
2017-11-16Rollup merge of #45951 - CrockAgile:master, r=michaelwoeristerGuillaume Gomez-145/+75
incr: Update hash tests to use `except`-style checking Part of #44924 r? @michaelwoerister
2017-11-14Remove checked arithmetic from if expression hash testsJeff Crocker-4/+4
2017-11-14Rollup merge of #45950 - ↵Guillaume Gomez-112/+56
fitzgen:update-unary-and-binary-exprs-test-to-use-incr-except, r=michaelwoerister incr: Make `unary_and_binary_exprs.rs` use `except`-style incremental checking Part of #44924 r? @michaelwoerister
2017-11-14update let-expressions to use exceptgaurikholkar-210/+36
2017-11-13fixing indentationgaurikholkar-12/+12
2017-11-12Updated exported incremental compilation hash testsJeff Crocker-12/+6
2017-11-12Fix indexing expressions test copy/paste docsJeff Crocker-1/+1
2017-11-12Update if-expressions incremental hash testsJeff Crocker-32/+16
2017-11-12incr: Make `unary_and_binary_exprs.rs` use `except`-style incremental checkingNick Fitzgerald-112/+56
Part of #44924
2017-11-12Update panic expressions w/o overflow checks testsJeff Crocker-52/+26
2017-11-12Update panic expression incremental testsJeff Crocker-44/+22
2017-11-12tidy fixesgaurikholkar-1/+1
2017-11-12update match-expressions.rsgaurikholkar-60/+47
2017-11-08Auto merge of #45867 - michaelwoerister:check-ich-stability, r=nikomatsakisbors-2/+37
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
2017-11-07incr.comp.: Acknowledge the fact that shift operations can panic at runtime.Michael Woerister-2/+37