…signature, r=workingjubilee

Error on invalid signatures for interrupt ABIs

We recently added `extern "custom"`, which must have type `fn()`. The various `extern "interrupt"` ABIs impose similar constraints on the signature of functions with that ABI: `x86-interrupt` should not have a return type (linting on the exact argument types is left as future work), and the other interrupt ABIs cannot have any parameters or a return type.

r? `@workingjubilee`

…signature, r=workingjubilee

Error on invalid signatures for interrupt ABIs

We recently added `extern "custom"`, which must have type `fn()`. The various `extern "interrupt"` ABIs impose similar constraints on the signature of functions with that ABI: `x86-interrupt` should not have a return type (linting on the exact argument types is left as future work), and the other interrupt ABIs cannot have any parameters or a return type.

r? ``@workingjubilee``

Rollup of 15 pull requests

Successful merges:

 - #135731 (Implement parsing of pinned borrows)
 - #138780 (Add `#[loop_match]` for improved DFA codegen)
 - #142453 (Windows: make `read_dir` stop iterating after the first error is encountered)
 - #142633 (Error on invalid signatures for interrupt ABIs)
 - #142768 (Avoid a bitcast FFI call in transmuting)
 - #142825 (Port `#[track_caller]` to the new attribute system)
 - #142844 (Enable short-ice for Windows)
 - #142934 (Tweak `-Zmacro-stats` measurement.)
 - #142955 (Couple of test suite fixes for cg_clif)
 - #142977 (rustdoc: Don't mark `#[target_feature]` functions as ⚠)
 - #142980 (Reduce mismatched-lifetime-syntaxes suggestions to MaybeIncorrect)
 - #142982 (Corrected spelling mistake in c_str.rs)
 - #142983 (Taint body on invalid call ABI)
 - #142988 (Update wasm-component-ld to 0.5.14)
 - #142993 (Update cargo)

r? `@ghost`
`@rustbot` modify labels: rollup

Rollup merge of #142633 - folkertdev:interrupt-abi-restrict-signature, r=workingjubilee

Error on invalid signatures for interrupt ABIs

We recently added `extern "custom"`, which must have type `fn()`. The various `extern "interrupt"` ABIs impose similar constraints on the signature of functions with that ABI: `x86-interrupt` should not have a return type (linting on the exact argument types is left as future work), and the other interrupt ABIs cannot have any parameters or a return type.

r? ```@workingjubilee```

…rn-nevermore, r=davidtwco

compiler: Allow `extern "interrupt" fn() -> !`

While reviewing rust-lang#142633 I overlooked a few details because I was kind of excited.

- Fixes rust-lang#143072

…rn-nevermore, r=davidtwco

compiler: Allow `extern "interrupt" fn() -> !`

While reviewing rust-lang#142633 I overlooked a few details because I was kind of excited.

- Fixes rust-lang#143072

…rn-nevermore, r=davidtwco

compiler: Allow `extern "interrupt" fn() -> !`

While reviewing rust-lang#142633 I overlooked a few details because I was kind of excited.

- Fixes rust-lang#143072

…rn-nevermore, r=davidtwco

compiler: Allow `extern "interrupt" fn() -> !`

While reviewing rust-lang#142633 I overlooked a few details because I was kind of excited.

- Fixes rust-lang#143072

Rollup merge of #143075 - workingjubilee:interrupts-may-return-nevermore, r=davidtwco

compiler: Allow `extern "interrupt" fn() -> !`

While reviewing #142633 I overlooked a few details because I was kind of excited.

- Fixes #143072