diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-11 19:35:28 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-11 19:35:28 +0100 |
| commit | 9746ac5c2f59b557e15b3c48e2b2b0cf4e17b64a (patch) | |
| tree | 06987bf348c8ff552f92f753047b389c2bc12aa7 /compiler/rustc_builtin_macros/src/log_syntax.rs | |
| parent | 8a2e3acb450ccbd361394c31334d5b361b28b8fa (diff) | |
| parent | e5dc1e378619b11b296a953ca08abb2cdf38f9e0 (diff) | |
| download | rust-9746ac5c2f59b557e15b3c48e2b2b0cf4e17b64a.tar.gz rust-9746ac5c2f59b557e15b3c48e2b2b0cf4e17b64a.zip | |
Rollup merge of #138002 - 1c3t3a:fix-std-cfi-violation, r=rcvalle
Disable CFI for weakly linked syscalls Currently, when enabling CFI via -Zsanitizer=cfi and executing e.g. std::sys::random::getrandom, we can observe a CFI violation. This is the case for all consumers of the std::sys::pal::weak::syscall macro, as it is defining weak functions which don't show up in LLVM IR metadata. CFI fails for all these functions. Similar to other such cases in https://github.com/rust-lang/rust/issues/115199, this change stops emitting the CFI typecheck for consumers of the macro via the `#[no_sanitize(cfi)]` attribute. r? ``````@rcvalle``````
Diffstat (limited to 'compiler/rustc_builtin_macros/src/log_syntax.rs')
0 files changed, 0 insertions, 0 deletions