diff options
| author | bors <bors@rust-lang.org> | 2022-07-24 01:22:36 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-07-24 01:22:36 +0000 |
| commit | db8086eb6056f022d3bb719f777307e9daa3f8d8 (patch) | |
| tree | 34b77df8f88f3024355caf7fc954e1bcccb7f2a5 /compiler/rustc_codegen_llvm/src/allocator.rs | |
| parent | fcad91868a515c51d0762bf6c7af2bedc11cc348 (diff) | |
| parent | f792f26a384cb036199ad30a57a2be22a9feef47 (diff) | |
| download | rust-db8086eb6056f022d3bb719f777307e9daa3f8d8.tar.gz rust-db8086eb6056f022d3bb719f777307e9daa3f8d8.zip | |
Auto merge of #95548 - rcvalle:rust-cfi-2, r=nagisa
Add fine-grained LLVM CFI support to the Rust compiler This PR improves the LLVM Control Flow Integrity (CFI) support in the Rust compiler by providing forward-edge control flow protection for Rust-compiled code only by aggregating function pointers in groups identified by their return and parameter types. Forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space) will be provided in later work as part of this project by identifying C char and integer type uses at the time types are encoded (see Type metadata in the design document in the tracking issue https://github.com/rust-lang/rust/issues/89653). LLVM CFI can be enabled with -Zsanitizer=cfi and requires LTO (i.e., -Clto). Thank you again, `@eddyb,` `@nagisa,` `@pcc,` and `@tmiasko` for all the help!
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/allocator.rs')
0 files changed, 0 insertions, 0 deletions