rust/compiler/rustc_codegen_llvm/src/allocator.rs, branch 1.71.1

Prevent insta-stable no alloc shim support

2023-05-11T14:35:09+00:00

You will need to add the following as replacement for the old __rust_* definitions when not using the alloc shim. #[no_mangle] static __rust_no_alloc_shim_is_unstable: u8 = 0;

Use global_fn_name instead of format!

2023-05-11T14:35:09+00:00

Split AllocatorKind::fn_name in global_fn_name and default_fn_name

2023-05-11T14:35:08+00:00

Don't use an allocator shim for `#[global_allocator]`

2023-05-11T14:23:31+00:00

This makes it possible to use liballoc/libstd in combination with `--emit obj` if you use `#[global_allocator]`. Making it work for the default libstd allocator would require weak functions, which are not well supported on all systems.

Revert "Remove #[alloc_error_handler] from the compiler and library"

2023-04-24T22:08:35+00:00

This reverts commit abc0660118cc95f47445fd33502a11dd448f5968.

Remove #[alloc_error_handler] from the compiler and library

2023-04-16T15:35:50+00:00

Add LLVM KCFI support to the Rust compiler

2022-12-09T01:24:39+00:00

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>

Rewrite implementation of `#[alloc_error_handler]`

2022-10-31T16:32:57+00:00

The new implementation doesn't use weak lang items and instead changes `#[alloc_error_handler]` to an attribute macro just like `#[global_allocator]`. The attribute will generate the `__rg_oom` function which is called by the compiler-generated `__rust_alloc_error_handler`. If no `__rg_oom` function is defined in any crate then the compiler shim will call `__rdl_oom` in the alloc crate which will simply panic. This also fixes link errors with `-C link-dead-code` with `default_alloc_error_handler`: `__rg_oom` was previously defined in the alloc crate and would attempt to reference the `oom` lang item, even if it didn't exist. This worked as long as `__rg_oom` was excluded from linking since it was not called. This is a prerequisite for the stabilization of `default_alloc_error_handler` (#102318).

Rename `debugging_opts` to `unstable_opts`

2022-07-13T22:47:06+00:00

This is no longer used only for debugging options (e.g. `-Zoutput-width`, `-Zallow-features`). Rename it to be more clear.

Auto merge of #88098 - Amanieu:oom_panic, r=nagisa

2022-03-18T03:01:46+00:00

Implement -Z oom=panic This PR removes the `#[rustc_allocator_nounwind]` attribute on `alloc_error_handler` which allows it to unwind with a panic instead of always aborting. This is then used to implement `-Z oom=panic` as per RFC 2116 (tracking issue #43596). Perf and binary size tests show negligible impact.