diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-09-30 21:53:35 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-30 21:53:35 +0200 |
| commit | b21c438eb506d803354af91ca1fc34e47713d799 (patch) | |
| tree | e27c88faaa1da02ee3ed6bee968f90df48b221f5 /compiler/rustc_transmute | |
| parent | 014e0af1497aaa932fc6c51eb4b2e6f9e9fab63f (diff) | |
| parent | 06a7460455284aca27fbf65505c385e3dc275da3 (diff) | |
| download | rust-b21c438eb506d803354af91ca1fc34e47713d799.tar.gz rust-b21c438eb506d803354af91ca1fc34e47713d799.zip | |
Rollup merge of #146635 - Zalathar:llvm-cov, r=SparrowLii
cg_llvm: Stop using `as_c_char_ptr` for coverage-related bindings [As explained by a note in `ffi.rs`](https://github.com/rust-lang/rust/blob/8a1b39995e5b630c5872f5de5079f1f569bd5ac2/compiler/rustc_codegen_llvm/src/llvm/ffi.rs#L4-L11), passing strings and byte slices through FFI is more convenient if we take advantage of the fact that `*const c_uchar` and `*const c_char` have the same ABI. Doing so avoids having to rely on a special helper function, since we can just call `as_ptr` instead. (The same logic applies to every other binding that currently uses the `as_c_char_ptr` helper; I just haven't adjusted all of them yet.) --- As a drive-by change, this PR also marks some coverage-related FFI bindings as `safe`.
Diffstat (limited to 'compiler/rustc_transmute')
0 files changed, 0 insertions, 0 deletions