about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/attributes.rs
diff options
context:
space:
mode:
authorLeón Orell Valerian Liehr <me@fmease.dev>2025-06-10 16:54:52 +0200
committerGitHub <noreply@github.com>2025-06-10 16:54:52 +0200
commita2badebce5d85fc2b2b01a59c7099b4e638dcf68 (patch)
tree82cd084684c3157b3df4ab0c29bdf0f5be9f37f3 /compiler/rustc_codegen_llvm/src/attributes.rs
parentf76f1f289d16126eaad56b50aa6219d665c152a1 (diff)
parent8808a9c17ff8b41b3ac6d6f10be79d0325e356d4 (diff)
downloadrust-a2badebce5d85fc2b2b01a59c7099b4e638dcf68.tar.gz
rust-a2badebce5d85fc2b2b01a59c7099b4e638dcf68.zip
Rollup merge of #142271 - workingjubilee:fn-ptrs-have-two-different-lints, r=RalfJung
compiler: fn ptrs should hit different lints based on ABI

I was looking closer at the code for linting on ABIs and realized a mistake was probably made during rebase or review. I think that for function pointers in the HIR, the lint that fires should probably depend on the ABI we encountered, e.g. if it's on the newly-deprecated set of ABIs or not. This will be slightly confusing for a little bit, but I think we can do more to reduce that confusion by switching `unsupported_fn_ptr_calling_conventions` to a hard error.

r? ``@RalfJung``
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/attributes.rs')
0 files changed, 0 insertions, 0 deletions