rust/compiler/rustc_const_eval/src, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-20T20:14:27+00:00fix handling of base address for TypeId allocations2025-07-20T20:14:27+00:00Ralf Jungpost@ralfj.de2025-07-19T18:04:08+00:00urn:sha1:3f9be406a6fd879a99a0eba33cc196fa2cb3957binterpret: fix TypeId pointers being considered data pointers2025-07-19T08:29:13+00:00Ralf Jungpost@ralfj.de2025-07-19T08:29:13+00:00urn:sha1:7672e4ed85916d564d38dbd3a64803a45568504dRollup merge of #144123 - oli-obk:ctfe-unsize, r=RalfJung2025-07-18T17:14:47+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-07-18T17:14:47+00:00urn:sha1:a59efc61f92e2ee047f72fde2494664e9a1793b8
Generalize `unsize` and `unsize_into` destinations
Just something that I noticed during other work. We do this for most such functions, so let's do it here, too.
r? ``@RalfJung``
Rollup merge of #142673 - oli-obk:uninit-read-mem, r=RalfJung2025-07-18T17:14:43+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-07-18T17:14:43+00:00urn:sha1:b3827e4f3728b77bd3e60587487ebfc3cc8d901b
Show the offset, length and memory of uninit read errors
r? ``@RalfJung``
I want to improve memory dumps in general. Not sure yet how to do so best within rust diagnostics, but in a perfect world I could generate a dummy in-memory file (that contains the rendered memory dump) that we then can then provide regular rustc `Span`s to. So we'd basically report normal diagnostics for them with squiggly lines and everything.
Generalize `unsize` and `unsize_into` destinations2025-07-18T13:09:34+00:00Oli Scherergithub333195615777966@oli-obk.de2025-07-03T08:00:47+00:00urn:sha1:c65d3ce365ecb6d6f36b413edb591d4746f52305Show the memory of uninit reads2025-07-18T07:47:08+00:00Oli Scherergithub333195615777966@oli-obk.de2025-06-18T12:51:47+00:00urn:sha1:652ba279ecc693d8b4310c40e645a62009f5b0edRollup merge of #143293 - folkertdev:naked-function-kcfi, r=compiler-errors2025-07-18T02:27:51+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-07-18T02:27:51+00:00urn:sha1:accf61dd42548bd5ec61d43f246b3eb499e980dd
fix `-Zsanitizer=kcfi` on `#[naked]` functions
fixes https://github.com/rust-lang/rust/issues/143266
With `-Zsanitizer=kcfi`, indirect calls happen via generated intermediate shim that forwards the call. The generated shim preserves the attributes of the original, including `#[unsafe(naked)]`. The shim is not a naked function though, and violates its invariants (like having a body that consists of a single `naked_asm!` call).
My fix here is to match on the `InstanceKind`, and only use `codegen_naked_asm` when the instance is not a `ReifyShim`. That does beg the question whether there are other `InstanceKind`s that could come up. As far as I can tell the answer is no: calling via `dyn` seems to work find, and `#[track_caller]` is disallowed in combination with `#[naked]`.
r? codegen
````@rustbot```` label +A-naked
cc ````@maurer```` ````@rcvalle````
Report the range of uninit bytes in CTFE errors2025-07-17T20:00:51+00:00Oli Scherergithub333195615777966@oli-obk.de2025-06-18T12:51:47+00:00urn:sha1:12eedafc38b1d3af02c9c15333d0ba2f1aee1253Auto merge of #143879 - fee1-dead-contrib:push-lrlpoouyqqry, r=fmease2025-07-17T15:54:33+00:00borsbors@rust-lang.org2025-07-17T15:54:33+00:00urn:sha1:9cd918bcbbc26deb005eb4e1bd9a445380195e56
parse `const trait Trait`
r? oli-obk or anyone from project-const-traits
cc `@rust-lang/project-const-traits`
parse `const trait Trait`2025-07-17T10:06:26+00:00Deadbeefent3rm4n@gmail.com2025-07-13T08:49:19+00:00urn:sha1:69326878eeabb713e2d4a85215b87f18e498313c