diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-11 07:05:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-11 07:05:27 +0200 |
| commit | 39761b0cf9c603beb7862e6c7cbb796defb2be90 (patch) | |
| tree | 233f44f06ecfd34b1414b1cb5ca380f364e35a5b /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | aa9adf457b85a4c75f3b0f791338395b1bd367e5 (diff) | |
| parent | 9addf0651c2fc9174824ea7e28c2651c780ae968 (diff) | |
| download | rust-39761b0cf9c603beb7862e6c7cbb796defb2be90.tar.gz rust-39761b0cf9c603beb7862e6c7cbb796defb2be90.zip | |
Rollup merge of #111382 - Zalathar:ffi, r=cuviper
Isolate coverage FFI type layouts from their underlying LLVM C++ types I noticed that several of the types used to send coverage information through FFI are not properly isolated from the layout of their corresponding C++ types in the LLVM API. This PR adds more explicitly-defined FFI struct/enum types in `CoverageMappingWrapper.cpp`, so that Rust source files in `rustc_codegen_ssa` and `rustc_codegen_llvm` aren't directly exposed to LLVM C++ types.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions