diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-08-11 01:56:39 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-08-11 01:56:39 +0200 |
| commit | 9edec571cbaa0b99ce4640b733629fc05b4524b0 (patch) | |
| tree | 940dfc315b640ad77d4d24268e24a4bf2285a90e /compiler/rustc_codegen_llvm/src | |
| parent | 1e41af3c8c3195afc1bffb1a807e05cb31810c9f (diff) | |
| parent | fd3851aadb3f5326480f9e9ced57ade2db86480b (diff) | |
| download | rust-9edec571cbaa0b99ce4640b733629fc05b4524b0.tar.gz rust-9edec571cbaa0b99ce4640b733629fc05b4524b0.zip | |
Rollup merge of #75339 - RalfJung:eval-required, r=oli-obk
evaluate required_consts when pushing stack frame in Miri engine [Just like codegen](https://github.com/rust-lang/rust/pull/70820/files#diff-32c57af5c8e23eb048f55d1e955e5cd5R194), Miri needs to make sure all `required_consts` evaluate successfully, to catch post-monomorphization errors. While at it I also moved the const_eval error reporting logic into rustc_mir::const_eval::error; there is no reason it should be in `rustc_middle`. I kept this in a separate commit for easier reviewing. Helps with https://github.com/rust-lang/miri/issues/1382. I will add a test on the Miri side (done now: https://github.com/rust-lang/miri/pull/1504). r? @oli-obk
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions