| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-04-29 | Bless tests | Dylan MacKenzie | -1/+0 | |
| 2020-02-15 | remove no-longer-needed test | Ralf Jung | -20/+0 | |
| 2020-02-15 | fix compile-fail | Ralf Jung | -4/+4 | |
| 2020-01-09 | Update tests | Vadim Petrochenkov | -0/+1 | |
| 2019-12-07 | Auto merge of #66927 - RalfJung:engines-dont-panic, r=oli-obk | bors | -1/+0 | |
| Miri core engine: use throw_ub instead of throw_panic See https://github.com/rust-lang/rust/issues/66902 for context: panicking is not really an "interpreter error", but just part of a normal Rust execution. This is a first step towards removing the `InterpError::Panic` variant: the core Miri engine does not use it any more. ConstProp and ConstEval still use it, though. This will be addressed in future PRs. From what I can tell, all the error messages this removes are actually duplicates. r? @oli-obk @wesleywiser | ||||
| 2019-12-02 | Correct other tests related to const_mut_refs | Christian Poveda | -1/+1 | |
| 2019-12-01 | fix compile-fail tests | Ralf Jung | -1/+0 | |
| 2019-11-15 | A `Downcast` is now reached when const-checking a `for` loop | Dylan MacKenzie | -0/+1 | |
| I believe this occurs because the old checker stopped processing basic blocks after a `SwitchInt`. | ||||
| 2019-11-13 | Bless less verbose error messages | Dylan MacKenzie | -2/+0 | |
| The MIR const-checker errors for if/match/loop are now delay span bugs, so nothing will be emitted unless the HIR checker misses something. | ||||
| 2019-11-13 | Bless const tests with improved diagnostics | Dylan MacKenzie | -0/+1 | |
| 2019-10-18 | [const-prop] Handle MIR Rvalue::Aggregates | Wesley Wiser | -0/+1 | |
| 2019-08-06 | move error with diverging output to compile-fail | Esteban Küber | -0/+48 | |
