rust/compiler/rustc_codegen_llvm/src/llvm, branch betahttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=beta2025-09-06T18:37:23+00:00Remove 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.
Update to ar_archive_writer 0.5.12025-08-29T23:37:42+00:00Daniel Paoliellodanpao@microsoft.com2025-08-21T18:40:45+00:00urn:sha1:da8f230d5f87a9a6113ed7774eec7f20268cf240Auto merge of #145877 - nikic:capture-address, r=tmiasko2025-08-28T00:01:22+00:00borsbors@rust-lang.org2025-08-28T00:01:22+00:00urn:sha1:d36f964125163c2e698de5559efefb8217b8b7f0
Use captures(address) instead of captures(none) for indirect args
While provenance cannot be captured through these arguments, the address / object identity can.
Fixes https://github.com/rust-lang/rust/issues/137668.
r? `@ghost`
Use captures(address) instead of captures(none) for indirect args2025-08-26T14:16:23+00:00Nikita Popovnpopov@redhat.com2025-08-26T09:13:03+00:00urn:sha1:c3ab409b4fa3b1fb18f34877d9811bb502ed507f
While provenance cannot be captured through these arguments, the
address / object identity can.
Assert that LLVM range-attribute values don't exceed 128 bits2025-08-26T03:07:19+00:00ZalatharZalathar@users.noreply.github.com2025-08-26T02:31:33+00:00urn:sha1:fcff8f7f5a0d4add3c05f57de1b34291746c3c08
The underlying implementation of `LLVMCreateConstantRangeAttribute` assumes
that each of `LowerWords` and `UpperWords` points to enough u64 values to
define an integer of the specified bit-length, and will encounter UB if that is
not the case.
Our safe wrapper function always passes pointers to `[u64; 2]` arrays,
regardless of the bit-length specified. That's fine in practice, because scalar
primitives never exceed 128 bits, but it is technically a soundness hole in a
safe function.
We can close the soundness hole by explicitly asserting `size_bits <= 128`.
This is effectively just a stricter version of the existing check that the
value must be small enough to fit in `c_uint`.
Rename `llvm::Bool` aliases to standard const case2025-08-24T13:09:54+00:00ZalatharZalathar@users.noreply.github.com2025-08-24T10:49:32+00:00urn:sha1:b4e97e5d866dd43c110d337affc419d5ac482765
This avoids the need for `#![allow(non_upper_case_globals)]`.
Replace the `llvm::Bool` typedef with a proper newtype2025-08-24T13:09:54+00:00ZalatharZalathar@users.noreply.github.com2025-08-24T05:05:26+00:00urn:sha1:455a67bd4f38b10e613fc6e2103598db10ad57feTell LLVM about read-only captures2025-08-20T17:08:16+00:00Nikita Popovnpopov@redhat.com2025-08-11T15:18:23+00:00urn:sha1:d71ed8d19bcfdbd6eb3bf2620071f2ab95470a57
`&Freeze` parameters are not only `readonly` within the function,
but any captures of the pointer can also only be used for reads.
This can now be encoded using the `captures(address, read_provenance)`
attribute.
Rollup merge of #145484 - Zalathar:archive-builder, r=bjorn32025-08-19T04:18:25+00:00Stuart CookZalathar@users.noreply.github.com2025-08-19T04:18:25+00:00urn:sha1:8748d8e7d5b63932e3062361f736ff436c86be1f
Remove `LlvmArchiveBuilder` and supporting code/bindings
Switching over to the newer Rust-based `ArArchiveBuilder` happened in rust-lang/rust#128936, a year ago.
Per the comment in `new_archive_builder`, that seems like enough time to justify removing the older, unused `LlvmArchiveBuilder` implementation and its associated bindings.
Fixes rust-lang/rust#128955.
Rollup merge of #145432 - Zalathar:target-machine, r=wesleywiser2025-08-19T04:18:25+00:00Stuart CookZalathar@users.noreply.github.com2025-08-19T04:18:25+00:00urn:sha1:8945924d77065c96d35f81bc19a0b9040664bb57
cg_llvm: Small cleanups to `owned_target_machine`
This PR contains a few tiny cleanups to the `owned_target_machine` code.
Each individual commit should be fairly straightforward.