rust/compiler/rustc_const_eval/src
bors ff55fa3026 Auto merge of #113124 - nbdd0121:eh_frame, r=cjgillot
Add MIR validation for unwind out from nounwind functions + fixes to make validation pass

`@Nilstrieb`  This is the MIR validation you asked in https://github.com/rust-lang/rust/pull/112403#discussion_r1222739722.

Two passes need to be fixed to get the validation to pass:
* `RemoveNoopLandingPads` currently unconditionally introduce a resume block (even there is none to begin with!), changed to not do that
* Generator state transform introduces a `assert` which may unwind, and its drop elaboration also introduces many new `UnwindAction`s, so in this case run the AbortUnwindingCalls after the transformation.

I believe this PR should also fix Rust-for-Linux/linux#1016, cc `@ojeda`

r? `@Nilstrieb`
2023-08-20 09:58:52 +00:00
..
const_eval const-eval: ensure we never const-execute a function marked rustc_do_not_const_check 2023-08-19 14:33:31 +02:00
interpret Rollup merge of #114615 - RalfJung:interpret-invalid-where, r=lcnr 2023-08-08 21:44:45 +02:00
transform Add missing instantiation of generator ty in validator 2023-08-18 16:40:10 +01:00
util Turns out opaque types can have hidden types registered during mir validation 2023-07-27 08:23:06 +00:00
errors.rs interpret: remove incomplete protection against invalid where clauses 2023-08-08 10:35:22 +02:00
lib.rs Name the destructure_mir_constant query appropriately 2023-07-05 15:54:43 +00:00