diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-08-08 18:57:00 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-08 18:57:00 +0200 |
| commit | 2d7075cf0018f7dc642cb2909deba764c36713dc (patch) | |
| tree | 7b9b931275d42d98017ea4689c5f09166512d04f /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 3a9dd829d0b59ff6b8516a5464042ff54cc09145 (diff) | |
| parent | 470ada2de0ec507191ad8da35b0712986646d01c (diff) | |
| download | rust-2d7075cf0018f7dc642cb2909deba764c36713dc.tar.gz rust-2d7075cf0018f7dc642cb2909deba764c36713dc.zip | |
Rollup merge of #128612 - compiler-errors:validate-mir-opt-mir, r=davidtwco
Make `validate_mir` ensure the final MIR for all bodies A lot of the crashes tests use `-Zpolymorphize` or `-Zdump-mir` for their side effect of computing the `optimized_mir` for all bodies, which will uncover bugs with late MIR passes like the inliner. I don't like having all these tests depend on `-Zpolymorphize` (or other hacky ways) for no reason, so this PR extends the `-Zvalidate-mir` flag to ensure `optimized_mir`/`mir_for_ctfe` for all body owners during the analysis phase. Two thoughts: 1. This could be moved later in the compilation pipeline I guess? I don't really think it matters, though. 1. This could alternatively be expressed using a new flag, though I don't necessarily see much value in separating these. For example, #128171 could have used this flag, in the `tests/ui/polymorphization/inline-incorrect-early-bound.rs`. r? mir
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions