diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2025-01-12 12:07:58 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-12 12:07:58 +0100 |
| commit | 988137c040d851df2715d48d1099d456c401f6d1 (patch) | |
| tree | 5561f36ad06dfe744cb75ba999fe6e2f5dfc9d8e /compiler/rustc_codegen_gcc/example/alloc_example.rs | |
| parent | 55503a1d0eee2cd9c8ea2749da06a530baa38b97 (diff) | |
| parent | f1d622678b330ba7640d76a8adbf5a2fdbee73cc (diff) | |
| download | rust-988137c040d851df2715d48d1099d456c401f6d1.tar.gz rust-988137c040d851df2715d48d1099d456c401f6d1.zip | |
Rollup merge of #135377 - compiler-errors:impossible-step, r=oli-obk
Make MIR cleanup for functions with impossible predicates into a real MIR pass It's a bit jarring to see the body of a function with an impossible-to-satisfy where clause suddenly go to a single `unreachable` terminator when looking at the MIR dump output in order, and I discovered it's because we manually replace the body outside of a MIR pass. Let's make it into a fully flegded MIR pass so it's more clear what it's doing and when it's being applied.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions