diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-08-06 11:21:31 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-08-06 11:21:31 +0900 |
| commit | 71ad503fd9ce83d47aba75e0569598ee9406df78 (patch) | |
| tree | 289346ff69ac7a6c79b2f8a67feede414f039e80 /compiler/rustc_codegen_gcc | |
| parent | 5b4396068744e810d090de038e6f456432d203a2 (diff) | |
| parent | a96fd577a44845df221c81ff24b35819135b4a0d (diff) | |
| download | rust-71ad503fd9ce83d47aba75e0569598ee9406df78.tar.gz rust-71ad503fd9ce83d47aba75e0569598ee9406df78.zip | |
Rollup merge of #87742 - npmccallum:naked_ffi, r=Amanieu
Validate FFI-safety warnings on naked functions Test that FFI-safety warnings don't get accidentally dropped on naked functions. The big picture is that if you implement a naked function with the Rust ABI you'll get a warning. Further, if you implement a naked function with a standardized ABI, but use non-FFI-safe types you will still get a warning. rust-lang/rfcs#2774 rust-lang/rfcs#2972 cc ``````@joshtriplett`````` ``````@Amanieu`````` ``````@haraldh``````
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions