rust/compiler/rustc_codegen_llvm/src/back, branch cargo_update https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=cargo_update 2025-09-25T08:10:55+00:00 Use `LLVMDisposeTargetMachine` 2025-09-25T08:10:55+00:00 Zalathar Zalathar@users.noreply.github.com 2025-09-25T08:10:55+00:00 urn:sha1:85018f09f67bd54868fe12a4632bbd637a474853 Add self-profile events for target-machine creation 2025-09-21T11:37:15+00:00 Zalathar Zalathar@users.noreply.github.com 2025-09-21T10:50:44+00:00 urn:sha1:b17fb70d0437b90fc9ada0ac2d924cce06eb8828 These code paths are surprisingly hot in the `large-workspace` benchmark; it would be handy to see some detailed timings and execution counts. Move target machine command-line quoting from C++ to Rust 2025-09-18T05:25:25+00:00 Zalathar Zalathar@users.noreply.github.com 2025-09-17T03:46:46+00:00 urn:sha1:8b0a25486040b91ede0120ff5a797517e0973895 Make llvm_enzyme a regular cargo feature 2025-09-15T15:31:56+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-09-15T15:31:56+00:00 urn:sha1:1991779bd4a0a8d8905b6644b06aa317dde353ac This makes it clearer that it is set by the build system rather than by the rustc that compiles the current rustc. It also avoids bootstrap needing to pass --check-cfg llvm_enzyme to rustc. Remove want_summary argument from prepare_thin 2025-09-06T18:37:23+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-09-04T15:16:55+00:00 urn:sha1:f2933b34a8331204270fa2bdbdcfd79fcffbb302 It is always false nowadays. ThinLTO summary writing is instead done by llvm_optimize. Remove thin_link_data method from ThinBufferMethods 2025-09-06T18:37:23+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-08-15T13:12:19+00:00 urn:sha1:e3d0b7d6480d7e4dbbbea24635f56e28dfe735b3 It is only used within cg_llvm. Ensure fat LTO doesn't merge everything into the allocator module 2025-09-06T13:31:41+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-09-05T19:09:39+00:00 urn:sha1:2cf94b92ca852924ad90943a0c469f01742216a6 Special case allocator module submission to avoid special casing it elsewhere 2025-09-04T08:21:10+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-08-28T10:26:29+00:00 urn: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. Update to ar_archive_writer 0.5.1 2025-08-29T23:37:42+00:00 Daniel Paoliello danpao@microsoft.com 2025-08-21T18:40:45+00:00 urn:sha1:da8f230d5f87a9a6113ed7774eec7f20268cf240 Move ___asan_globals_registered export 2025-08-28T19:36:51+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-08-28T18:05:47+00:00 urn:sha1:23e72ab41e27842eae0d60a6f4750c5151aabcbc All other sanitizer symbols are handled in prepare_lto already.