diff options
| author | bors <bors@rust-lang.org> | 2024-10-22 03:24:40 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-10-22 03:24:40 +0000 |
| commit | f03f7c6c9d9320e56355e043e20b0436b0db701a (patch) | |
| tree | 2cb44bd2658949cdd2494cf5bed94a0f25dd86ce /compiler/rustc_codegen_llvm/src | |
| parent | 1d0dad5eb330214e6cff1408289d426878ba2ba6 (diff) | |
| parent | aab0eee4ef30a2553770ae8d9b9ad352783d7720 (diff) | |
| download | rust-f03f7c6c9d9320e56355e043e20b0436b0db701a.tar.gz rust-f03f7c6c9d9320e56355e043e20b0436b0db701a.zip | |
Auto merge of #129935 - RalfJung:unsupported_calling_conventions, r=compiler-errors
make unsupported_calling_conventions a hard error This has been a future-compat lint (not shown in dependencies) since Rust 1.55, released 3 years ago. Hopefully that was enough time so this can be made a hard error now. Given that long timeframe, I think it's justified to skip the "show in dependencies" stage. There were [not many crates hitting this](https://github.com/rust-lang/rust/pull/86231#issuecomment-866300943) even when the lint was originally added. This should get cratered, and I assume then it needs a t-compiler FCP. (t-compiler because this looks entirely like an implementation oversight -- for the vast majority of ABIs, we already have a hard error, but some were initially missed, and we are finally fixing that.) Fixes https://github.com/rust-lang/rust/pull/87678
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
