Matthias Krüger 2d7075cf00
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
2024-08-08 18:57:00 +02:00
..
2024-04-26 17:20:16 +02:00
2024-04-18 18:55:20 +02:00
2024-04-19 23:09:37 +02:00
2024-04-19 23:09:37 +02:00
2024-04-19 23:09:37 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 18:55:20 +02:00
2024-04-19 23:09:37 +02:00
2024-04-19 23:09:37 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-06-30 17:08:45 +00:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-05-29 17:06:54 +01:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-05-29 17:06:54 +01:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-21 21:04:32 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-21 21:04:32 +02:00
2024-04-19 23:09:37 +02:00
2024-04-21 21:04:32 +02:00
2024-04-21 21:04:32 +02:00
2024-04-21 21:04:32 +02:00
2024-04-26 17:20:16 +02:00
2024-04-26 17:20:16 +02:00
2024-04-26 17:20:16 +02:00
2024-04-26 17:20:16 +02:00
2024-05-18 23:56:57 +02:00
2024-05-18 23:56:57 +02:00
2024-06-28 14:20:43 -04:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-16 20:38:08 +02:00
2024-06-16 20:38:08 +02:00
2024-06-16 20:38:08 +02:00
2024-06-16 20:38:08 +02:00
2024-06-16 20:38:08 +02:00
2024-06-16 20:38:08 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-04 23:44:10 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-08-04 21:25:49 +02:00
2024-08-04 21:25:49 +02:00
2024-08-04 21:25:49 +02:00
2024-08-04 21:25:49 +02:00
2024-08-04 21:25:49 +02:00

This is serves as a collection of crashes so that accidental ICE fixes are tracked. This was formally done at https://github.com/rust-lang/glacier but doing it inside the rustc testsuite is more convenient.

It is imperative that a test in the suite causes an internal compiler error/panic or makes rustc crash in some other way. A test will "pass" if rustc exits with something other than 1 or 0.

When adding crashes from https://github.com/rust-lang/rust/issues, the issue number should be noted in the file name (12345.rs should suffice) and perhaps also inside the file via //@ known-bug #4321

If you happen to fix one of the crashes, please move it to a fitting subdirectory in tests/ui and give it a meaningful name. Also please add a doc comment at the top of the file explaining why this test exists. :) Adding Fixes #NNNNN Fixes #MMMMM to the description of your pull request will ensure the corresponding tickets will be closed automatically upon merge. The ticket ids can be found in the file name or the known-bug annotation inside the testfile.