diff options
| author | bors <bors@rust-lang.org> | 2023-05-25 16:59:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-25 16:59:57 +0000 |
| commit | a2b1646c597329d0a25efa3889b66650f65de1de (patch) | |
| tree | f09c5d967f915501387578d1d89574c68343eeb8 /compiler/rustc_privacy/messages.ftl | |
| parent | cade26637fe1c23965ce644299ed5200db7c92dd (diff) | |
| parent | 33d9b5880885862fdf4ec5bf70f45bf0e503a7fc (diff) | |
| download | rust-a2b1646c597329d0a25efa3889b66650f65de1de.tar.gz rust-a2b1646c597329d0a25efa3889b66650f65de1de.zip | |
Auto merge of #86844 - bjorn3:global_alloc_improvements, r=pnkfelix
Support #[global_allocator] without the allocator shim This makes it possible to use liballoc/libstd in combination with `--emit obj` if you use `#[global_allocator]`. This is what rust-for-linux uses right now and systemd may use in the future. Currently they have to depend on the exact implementation of the allocator shim to create one themself as `--emit obj` doesn't create an allocator shim. Note that currently the allocator shim also defines the oom error handler, which is normally required too. Once `#![feature(default_alloc_error_handler)]` becomes the only option, this can be avoided. In addition when using only fallible allocator methods and either `--cfg no_global_oom_handling` for liballoc (like rust-for-linux) or `--gc-sections` no references to the oom error handler will exist. To avoid this feature being insta-stable, you will have to define `__rust_no_alloc_shim_is_unstable` to avoid linker errors. (Labeling this with both T-compiler and T-lang as it originally involved both an implementation detail and had an insta-stable user facing change. As noted above, the `__rust_no_alloc_shim_is_unstable` symbol requirement should prevent unintended dependence on this unstable feature.)
Diffstat (limited to 'compiler/rustc_privacy/messages.ftl')
0 files changed, 0 insertions, 0 deletions
