https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2025-10-01T13:36:47+00:00 2025-10-01T13:36:47+00:00 daxpedda daxpedda@gmail.com 2025-10-01T12:47:42+00:00 urn:sha1:5b809b355c5c134e6848f800a2f8e692a3c10d44 2025-09-28T17:57:33+00:00 Antoni Boucher bouanto@zoho.com 2025-09-28T16:08:44+00:00 urn:sha1:7fcbc5ea465a4e280d3b7a84fc3f781e9a120ed0 2025-09-23T16:13:53+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-23T16:13:53+00:00 urn:sha1:8f11c4dadb9e240815ca25e613b17656ab665eda [win] Use find-msvc-tools instead of cc to find the linker and rc on Windows `find-msvc-tools` was factored out from `cc` to allow updating the use in `rustc_codegen_ssa` (finding the linker when running the Rust compiler) and `rustc_windows_rc` (finding the Windows Resource Compiler when running the Rust compiler) to be separate from the use in `rustc_llvm` (building LLVM as part of building the Rust compiler). 2025-09-23T06:37:03+00:00 bors bors@rust-lang.org 2025-09-23T06:37:03+00:00 urn:sha1:40560823602064f4c726aea3e15e104449e1a392 Add panic=immediate-abort MCP: https://github.com/rust-lang/compiler-team/issues/909 This adds a new panic strategy, `-Cpanic=immediate-abort`. This panic strategy essentially just codifies use of `-Zbuild-std-features=panic_immediate_abort`. This PR is intended to just set up infrastructure, and while it will change how the compiler is invoked for users of the feature, there should be no other impacts. In many parts of the compiler, `PanicStrategy::ImmediateAbort` behaves just like `PanicStrategy::Abort`, because actually most parts of the compiler just mean to ask "can this unwind?" so I've added a helper function so we can say `sess.panic_strategy().unwinds()`. The panic and unwind strategies have some level of compatibility, which mostly means that we can pre-compile the sysroot with unwinding panics then the sysroot can be linked with aborting panics later. The immediate-abort strategy is all-or-nothing, enforced by `compiler/rustc_metadata/src/dependency_format.rs` and this is tested for in `tests/ui/panic-runtime/`. We could _technically_ be more compatible with the other panic strategies, but immediately-aborting panics primarily exist for users who want to eliminate all the code size responsible for the panic runtime. I'm open to other use cases if people want to present them, but not right now. This PR is already large. `-Cpanic=immediate-abort` sets both `cfg(panic = "immediate-abort")` _and_ `cfg(panic = "abort")`. bjorn3 pointed out that people may be checking for the abort cfg to ask if panics will unwind, and also the sysroot feature this is replacing used to require `-Cpanic=abort` so this seems like a good back-compat step. At least for the moment. Unclear if this is a good idea indefinitely. I can imagine this being confusing. The changes to the standard library attributes are purely mechanical. Apart from that, I removed an `unsafe` we haven't needed for a while since the `abort` intrinsic became safe, and I've added a helpful diagnostic for people trying to use the old feature. To test that `-Cpanic=immediate-abort` conflicts with other panic strategies, I've beefed up the core-stubs infrastructure a bit. There is now a separate attribute to set flags on it. I've added a test that this produces the desired codegen, called `tests/run-make-cargo/panic-immediate-abort-codegen/` and also a separate run-make-cargo test that checks that we can build a binary. 2025-09-21T17:12:18+00:00 Ben Kimock kimockb@gmail.com 2025-09-07T16:31:35+00:00 urn:sha1:888679013d1f424adef06267f3630069b4cabd40 2025-09-19T20:16:38+00:00 Alex Crichton alex@alexcrichton.com 2025-09-19T20:16:38+00:00 urn:sha1:f354d93abe1c404544c18585861518cf03188b0e This commit updates the target specification of wasm targets to set the `limit_rdylib_exports` value to `true` like it is on other native platforms. This was originally not implemented long ago as `wasm-ld` didn't have options for symbol exports, but since then it's grown a `--export` flag and such to control this. A custom case is needed in the linker implementation to handle wasm targets as `wasm-ld` doesn't support linker scripts used on other targets, but other than that the implementation is straightforward. The goal of this commit is enable building dynamic libraries on `wasm32-wasip2` which don't export every single symbol in the Rust standard library. Currently, without otherwise control over symbol visibility, all symbols end up being exported which generates excessively large binaries because `--gc-sections` ends up doing nothing as it's all exported anyway. 2025-09-19T19:00:30+00:00 Daniel Paoliello danpao@microsoft.com 2025-09-19T16:16:26+00:00 urn:sha1:4da59355fd88ba7d92b571c8b3a59c270e1aa7da 2025-09-12T18:53:28+00:00 Noratrieb 48135649+Noratrieb@users.noreply.github.com 2025-07-26T10:39:31+00:00 urn:sha1:f157ce994ea45e9faea9eff89c5f8b3d4ea77b6e This schema is helpful for people writing custom target spec JSON. It can provide autocomplete in the editor, and also serves as documentation when there are documentation comments on the structs, as `schemars` will put them in the schema. 2025-09-06T18:37:23+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-09-04T09:27:12+00:00 urn:sha1:3a1ae064a71f7e265e1e24c75b26fe3cd7edd3b1 2025-09-06T18:37:23+00:00 bjorn3 17426603+bjorn3@users.noreply.github.com 2025-09-04T15:16:55+00:00 urn:sha1:f2933b34a8331204270fa2bdbdcfd79fcffbb302 It is always false nowadays. ThinLTO summary writing is instead done by llvm_optimize.