rust/compiler/rustc_codegen_gcc/src, branch betahttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=beta2025-09-10T12:17:38+00:00Rollup merge of #146178 - folkertdev:static-align, r=jdonszelmann,ralfjung,traviscross2025-09-10T12:17:38+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-10T12:17:38+00:00urn:sha1:422c76adae98b55d13a07a8fb47d8bc47fa96fdf
Implement `#[rustc_align_static(N)]` on `static`s
Tracking issue: https://github.com/rust-lang/rust/issues/146177
```rust
#![feature(static_align)]
#[rustc_align_static(64)]
static SO_ALIGNED: u64 = 0;
```
We need a different attribute than `rustc_align` because unstable attributes are tied to their feature (we can't have two unstable features use the same unstable attribute). Otherwise this uses all of the same infrastructure as `#[rustc_align]`.
r? `@traviscross`
allow `#[rustc_align_static(N)]` on `static`s2025-09-09T19:54:54+00:00Folkert de Vriesfolkert@folkertdev.nl2025-06-07T20:56:22+00:00urn:sha1:cbacd00f106778830803ad2e2364518f06ff9078
We need a different attribute than `rustc_align` because unstable attributes are
tied to their feature (we can't have two unstable features use the same
unstable attribute). Otherwise this uses all of the same infrastructure
as `#[rustc_align]`.
erase_regions to erase_and_anonymize_regions2025-09-09T12:49:16+00:00Boxyrust@boxyuwu.dev2025-08-21T15:50:54+00:00urn:sha1:e379c7758667f900aaf5551c4553c7d4c121e3e1Remove 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.
Remove thin_link_data method from ThinBufferMethods2025-09-06T18:37:23+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-08-15T13:12:19+00:00urn:sha1:e3d0b7d6480d7e4dbbbea24635f56e28dfe735b3
It is only used within cg_llvm.
Special 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.
Fix sync conflict2025-08-26T15:25:45+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-08-26T15:25:45+00:00urn:sha1:a03a0f1d4421b77f0270686aa6e3a9d0602c48f8Merge commit 'feb42827f11a7ae241ceecc81e9ae556fb6ba214' into subtree-update_cg_gcc_2025-08-262025-08-26T15:18:15+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-08-26T15:18:15+00:00urn:sha1:17137135aeb281e3abf2c41740633aa3c4042e17Directly raise fatal errors inside the codegen backends2025-08-24T11:20:41+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-08-24T10:47:04+00:00urn:sha1:525c6a356284ea47587f0316cec23cab290b986e
As opposed to passing it around through Result.
Complete functionality and general cleanup2025-08-14T16:30:15+00:00Marcelo Domínguezdmmarcelo27@gmail.com2025-08-14T15:27:57+00:00urn:sha1:250d77e5d72fde69a6406050a3b037635f685378