rust/compiler/rustc_codegen_ssa/src/back/write.rs, branch cargo_updatehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=cargo_update2025-09-06T18:37:23+00:00Move timers into execute_*_work_item2025-09-06T18:37:23+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-09-04T09:27:12+00:00urn:sha1:3a1ae064a71f7e265e1e24c75b26fe3cd7edd3b1Remove want_summary argument from prepare_thin2025-09-06T18:37:23+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-09-04T15:16:55+00:00urn:sha1:f2933b34a8331204270fa2bdbdcfd79fcffbb302
It is always false nowadays. ThinLTO summary writing is instead done by
llvm_optimize.
Ensure fat LTO doesn't merge everything into the allocator module2025-09-06T13:31:41+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-09-05T19:09:39+00:00urn:sha1:2cf94b92ca852924ad90943a0c469f01742216a6Make the allocator shim participate in LTO again2025-09-06T08:35:55+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-09-05T09:32:56+00:00urn:sha1:027135976849da34250d7638502bcc2a24f741d7Special case allocator module submission to avoid special casing it elsewhere2025-09-04T08:21:10+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-08-28T10:26:29+00:00urn:sha1:319fe230f0d960b343be31a1182dc0f10753156c
A lot of places had special handling just in case they would get an
allocator module even though most of these places could never get one or
would have a trivial implementation for the allocator module. Moving all
handling of the allocator module to a single place simplifies things a
fair bit.
Ensure the allocator shim never participates in LTO2025-09-04T08:21:10+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-08-28T09:54:42+00:00urn:sha1:eea81b5d752f5310fcbd5ddae722afc7de0b8fa1
Making it participate in LTO would be incorrect if you compile a crate
as both a dylib (which needs it) and rlib (which must not include it) in
the same rustc invocation. With linker plugin LTO, the allocator shim
will still participate in LTO as it is safe to do so in that case.
Revert "Make `lto` and `linker-plugin-lto` work the same for `compiler_builtins`"2025-09-02T20:11:19+00:00Ramon de C Vallercvalle@users.noreply.github.com2025-09-02T18:23:48+00:00urn:sha1:916b55e08217ca14dabec0169067ed8d6523bf6e
This reverts commit cf8753e4f9c3597f04cd5d3aa261e4561d5378a6 and fixes the
regressions reported.
Rollup merge of #145368 - rcvalle:rust-cfi-fix-142284, r=dianqk2025-08-28T19:41:01+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-08-28T19:41:01+00:00urn:sha1:9e4a28361570e4793ae77effd24901013e92c29b
CFI: Make `lto` and `linker-plugin-lto` work the same for `compiler_builtins`
Fix rust-lang/rust#142284 by ensuring that `#![no_builtins]` crates can still emit bitcode when proper (i.e., non-rustc) LTO (i.e., -Clinker-plugin-lto) is used.
Make `lto` and `linker-plugin-lto` work the same for `compiler_builtins`2025-08-26T23:32:29+00:00Matthew Maurermmaurer@google.com2025-06-10T23:37:05+00:00urn:sha1:cf8753e4f9c3597f04cd5d3aa261e4561d5378a6
Fix #142284 by ensuring that `#![no_builtins]` crates can still emit bitcode
when proper (i.e., non-rustc) LTO (i.e., -Clinker-plugin-lto) is used.
Comment on intentional field order2025-08-26T16:18:39+00:00Daria Sukhoninadariasukhonina@gmail.com2025-08-26T16:18:39+00:00urn:sha1:dd07459096beddf523b86a7ef03e4703390a7319