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 | c5528ce64368630668c8bb0d3d827a9bd66ec21a (patch) | |
| tree | 7d2f0055cc8f1aea29822520b62ff98a1021efb3 /tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff | |
| parent | e5e7395cca92765ca56cefe83bce095ad4e6e0c0 (diff) | |
| parent | bfe3c24e9a303abb5aa1d30c890c81004636346a (diff) | |
| download | rust-c5528ce64368630668c8bb0d3d827a9bd66ec21a.tar.gz rust-c5528ce64368630668c8bb0d3d827a9bd66ec21a.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 'tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff')
0 files changed, 0 insertions, 0 deletions