https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try-perf 2025-07-20T17:15:14+00:00 2025-07-20T17:15:14+00:00 Scott McMurray scottmcm@users.noreply.github.com 2025-07-13T00:11:47+00:00 urn:sha1:493fd9a54110dc9d0d60566140e65f701070e34c 2025-06-30T08:04:19+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-06-21T11:26:27+00:00 urn:sha1:672e0bec9edfb174c93edafcfe46a8fa3c05c931 2025-06-16T23:04:37+00:00 David Wood david.wood2@arm.com 2025-03-05T04:31:12+00:00 urn:sha1:3d128856ce0cc12437285aad4f9b89958f044814 As in many previous commits, adding the new traits to minicore, but this time for cranelift and gcc. 2025-06-14T09:27:10+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-06-14T09:27:10+00:00 urn:sha1:db23a76217490844d404ba5931798df74fd0268e Unimplement unsized_locals Implements https://github.com/rust-lang/compiler-team/issues/630 Tracking issue here: https://github.com/rust-lang/rust/issues/111942 Note that this just removes the feature, not the implementation, and does not touch `unsized_fn_params`. This is because it is required to support `Box<dyn FnOnce()>: FnOnce()`. There may be more that should be removed (possibly in follow up prs) - the `forget_unsized` function and `forget` intrinsic. - the `unsized_locals` test directory; I've just fixed up the tests for now - various codegen support for unsized values and allocas cc ``@JakobDegen`` ``@oli-obk`` ``@Noratrieb`` ``@programmerjake`` ``@bjorn3`` ``@rustbot`` label F-unsized_locals Fixes rust-lang/rust#79409 2025-06-12T23:16:36+00:00 mejrs 59372212+mejrs@users.noreply.github.com 2025-06-12T23:16:36+00:00 urn:sha1:c0e02e26b39913ec1ee31621c65784542b137310 2025-06-12T15:50:25+00:00 Ralf Jung post@ralfj.de 2025-06-12T11:44:19+00:00 urn:sha1:62418f4c56e57a591d51ba24ccbd6c7271ce4cb5 2025-06-03T15:07:10+00:00 sayantn sayantn05@gmail.com 2025-06-03T15:07:10+00:00 urn:sha1:d91c1af24b551d5fead9fb7b9e2125574aab8b5c - remove unused `llvm.aarch64.neon.frintn` from cg_clif 2025-05-25T18:51:16+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-05-25T18:51:16+00:00 urn:sha1:3816385b09db445ab580043ed45218df8c1198ad 2025-04-24T06:14:36+00:00 bendn bend.n@outlook.com 2025-03-31T08:50:56+00:00 urn:sha1:c8c074288a277df21a52aded322dfa25bc283f64 2025-04-24T00:44:40+00:00 bors bors@rust-lang.org 2025-04-24T00:44:40+00:00 urn:sha1:c02a4f0852e6665cf3df3867982021383f5615df make abi_unsupported_vector_types a hard error Fixes https://github.com/rust-lang/rust/issues/116558 by completing the transition; see that issue for context. The lint was introduced with Rust 1.84 and this has been shown in cargo's future breakage reports since Rust 1.85, released 6 weeks ago, and so far we got 0 complaints by users. There's not even a backlink on the tracking issue. We did a [crater run](https://github.com/rust-lang/rust/pull/127731#issuecomment-2286736295) when the lint was originally added and found no breakage. So I don't think we need another crater run now, but I can do one if the team prefers that. https://github.com/rust-lang/rust/issues/131800 is done, so for most current targets (in particular, all tier 1 and tier 2 targets) we have the information to implement this check (modulo the targets where we don't properly support SIMD vectors yet, see the sub-issues of https://github.com/rust-lang/rust/issues/116558). If a new target gets added in the future, it will default to reject all SIMD vector types until proper information is added, which is the default we want. This will need approval by for `@rust-lang/lang.` Cc `@workingjubilee` `@veluca93` try-job: test-various try-job: armhf-gnu try-job: dist-i586-gnu-i586-i686-musl