rust/compiler/rustc_middle/src/mir/interpret, branch autohttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=auto2025-09-24T11:35:29+00:00const validation: better error for maybe-null references2025-09-24T11:35:29+00:00Ralf Jungpost@ralfj.de2025-09-24T10:12:41+00:00urn:sha1:8328c3dada0c888b1c570f97314b3f697d4b2a96const-eval: improve and actually test the errors when pointers might be outside the range of a scalar2025-09-24T11:34:33+00:00Ralf Jungpost@ralfj.de2025-09-22T17:46:30+00:00urn:sha1:0a41add6293d76b165968d70f95e7edbbe65fe11Auto merge of #146331 - RalfJung:copy-prov-repeat, r=oli-obk2025-09-17T13:56:54+00:00borsbors@rust-lang.org2025-09-17T13:56:54+00:00urn:sha1:5d1b897a07dc30d810dd541795125c1c216266c7
interpret: copy_provenance: avoid large intermediate buffer for large repeat counts
Copying provenance worked in this odd way where the "preparation" phase (which is supposed to just extract the necessary information from the source range) already did all the work of repeating the result N times for the target range. This was needed to use the existing `insert_presorted` function on `SortedMap`.
This PR generalizes `insert_presorted` so that we can avoid this odd structure on copy-provenance, and maybe even improve performance.
Rollup 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`
avoid calling insert_presorted more than once2025-09-10T06:40:12+00:00Ralf Jungpost@ralfj.de2025-09-08T14:10:37+00:00urn:sha1:7abbc9c8b2c638752e2a6b0913ed1e93e14d21bainterpret: copy_provenance: avoid large intermediate buffer for large repeat counts2025-09-10T06:40:12+00:00Ralf Jungpost@ralfj.de2025-09-08T13:56:48+00:00urn:sha1:64ea775d27599a33b070dd3aa4353e1e7faee0b4allow `#[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]`.
Auto merge of #145717 - BoxyUwU:erase_regions_rename, r=lcnr2025-09-09T15:04:44+00:00borsbors@rust-lang.org2025-09-09T15:04:44+00:00urn:sha1:364da5d88d772fa40fb20353443595385443ac25
rename erase_regions to erase_and_anonymize_regions
I find it consistently confusing that `erase_regions` does more than replacing regions with `'erased`. it also makes some code look real goofy to be writing manual folders to erase regions with a comment saying "we cant use erase regions" :> or code that re-calls erase_regions on types with regions already erased just to anonymize all the bound regions.
r? lcnr
idk how i feel about the name being almost twice as long now
erase_regions to erase_and_anonymize_regions2025-09-09T12:49:16+00:00Boxyrust@boxyuwu.dev2025-08-21T15:50:54+00:00urn:sha1:e379c7758667f900aaf5551c4553c7d4c121e3e1const-eval: disable pointer fragment support2025-09-08T11:22:52+00:00Ralf Jungpost@ralfj.de2025-09-08T08:40:18+00:00urn:sha1:aed0ed4c93d661fc7b66dc4a39690948476e8a4a