diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-09-21 14:42:34 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-21 14:42:34 +1000 |
| commit | 6333a8b9fe3a399ab70bff9ea1a26c31ce263649 (patch) | |
| tree | 80728b172440debb136976f45abbd47f765a6522 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | b0c55c8554c9a120e97e15941d552aa9b14af427 (diff) | |
| parent | 8b752cb37d646118c46f7739ae965b8e9c9a9b03 (diff) | |
| download | rust-6333a8b9fe3a399ab70bff9ea1a26c31ce263649.tar.gz rust-6333a8b9fe3a399ab70bff9ea1a26c31ce263649.zip | |
Rollup merge of #146551 - folkertdev:cmse-entry-c-variadic, r=workingjubilee
fix issue with `cmse-nonsecure-entry` ABI being both async and c-variadic tracking issue: https://github.com/rust-lang/rust/issues/75835 fixes https://github.com/rust-lang/rust/issues/132142 An `extern "cmse-nonsecure-entry"` function cannot be c-variadic (or, in any case, clang/LLVM does not support it, see https://godbolt.org/z/MaPjzGcE1). So just stop looking at the type if we know it'll be invalid anyway. I'm not entirely sure how to test this. The ICE is only possible on the `thumbv8m.main-none-eabi` and some related targets. I think using `minicore` is the most convenient, but use of `async` requires quite a long list of lang items to be present. Maybe we want that anyway though? On the other hand, it's extra `minicore` surface that might go out of date. An alternative is `run-make`, that should work, but is much less convenient. See also [#t-compiler/help > `async fn` and `minicore`](https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/.60async.20fn.60.20and.20.60minicore.60/with/539427262). r? `@ghost`
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions