rust/tests/ui/invalid/invalid-no-sanitize.stderr

error: invalid argument for `no_sanitize`
  --> $DIR/invalid-no-sanitize.rs:3:15
   |
LL | #[no_sanitize(brontosaurus)]
   |               ^^^^^^^^^^^^
   |
   = note: expected one of: `address`, `cfi`, `hwaddress`, `kcfi`, `memory`, `memtag`, `shadow-call-stack`, or `thread`

error: aborting due to previous error
Selectively disable sanitizer instrumentation Add `no_sanitize` attribute that allows to opt out from sanitizer instrumentation in an annotated function. 2020-01-11 18:00:00 -06:00			error: invalid argument for `no_sanitize`
			`--> $DIR/invalid-no-sanitize.rs:3:15`
			`\|`
			`LL \| #[no_sanitize(brontosaurus)]`
			`\| ^^^^^^^^^^^^`
			`\|`
Add LLVM KCFI support to the Rust compiler This commit adds LLVM Kernel Control Flow Integrity (KCFI) support to the Rust compiler. It initially provides forward-edge control flow protection for operating systems kernels for Rust-compiled code only by aggregating function pointers in groups identified by their return and parameter types. (See llvm/llvm-project@cff5bef.) 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 #89653). LLVM KCFI can be enabled with -Zsanitizer=kcfi. Co-authored-by: bjorn3 <17426603+bjorn3@users.noreply.github.com> 2022-11-21 23:29:00 -06:00			= note: expected one of: `address`, `cfi`, `hwaddress`, `kcfi`, `memory`, `memtag`, `shadow-call-stack`, or `thread`
Selectively disable sanitizer instrumentation Add `no_sanitize` attribute that allows to opt out from sanitizer instrumentation in an annotated function. 2020-01-11 18:00:00 -06:00
			`error: aborting due to previous error`