https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=stable 2025-08-29T02:55:20+00:00 2025-08-29T02:55:20+00:00 Wesley Wiser wwiser@gmail.com 2025-08-29T02:55:20+00:00 urn:sha1:161e29dc8486e69f8e02c1587a1abf141a413987 This reverts commit 49eda8edd5c99e4c65c687fff0b8e194eb339a23. 2025-07-31T12:19:27+00:00 Jana Dönszelmann jana@donsz.nl 2025-07-31T09:00:40+00:00 urn:sha1:e1d3ad89c7a2ad4f5d944a7fee1298ffe8c99645 2025-07-31T05:42:00+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-07-31T05:42:00+00:00 urn:sha1:5c123c25e36121730634aa59f8a66a5469d4d73f coverage: Re-land "Enlarge empty spans during MIR instrumentation" This allows us to assume that coverage spans will only be discarded during codegen in very unusual situations. --- This seemingly-simple change has a rather messy history: - rust-lang/rust#140847 - rust-lang/rust#141650 - rust-lang/rust#144298 - rust-lang/rust#144480 Since then, a number of related changes have landed that should make it reasonable to try again: - rust-lang/rust#144530 - rust-lang/rust#144560 - rust-lang/rust#144616 In particular, we have multiple fixes/mitigations, and a confirmed regression test for the original bug that is not triggered by re-landing the changes in this PR. 2025-07-31T05:42:00+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-07-31T05:42:00+00:00 urn:sha1:8628b78f24c01026d01b82afd3ec91a2019fe647 Implement support for `become` and explicit tail call codegen for the LLVM backend This PR implements codegen of explicit tail calls via `become` in `rustc_codegen_ssa` and support within the LLVM backend. Completes a task on (https://github.com/rust-lang/rust/issues/112788). This PR implements all the necessary bits to make explicit tail calls usable, other backends have received stubs for now and will ICE if you use `become` on them. I suspect there is some bikeshedding to be done on how we should go about implementing this for other backends, but it should be relatively straightforward for GCC after this is merged. During development I also put together a POC bytecode VM based on tail call dispatch to test these changes out and analyze the codegen to make sure it generates expected assembly. That is available [here](https://github.com/xacrimon/tcvm). 2025-07-30T03:17:05+00:00 Zalathar Zalathar@users.noreply.github.com 2025-05-04T04:09:52+00:00 urn:sha1:2e6f4a59226fd82c526df0f61fefc6fea44e7750 This allows us to assume that coverage spans will only be discarded during codegen in very unusual situations. 2025-07-29T10:19:49+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-07-29T10:19:49+00:00 urn:sha1:b3962e88114a5f633011d8670f318e1c20ba41b6 fix(debuginfo): disable overflow check for recursive non-enum types Commit b10edb4 introduce an overflow check when generating debuginfo for expanding recursive types. While this check works correctly for enums, it can incorrectly prune valid debug information for structures. For example see rust-lang/rust#143241 (https://github.com/rust-lang/rust/issues/143241#issuecomment-3073721477). Furthermore, for structures such check does not make sense, since structures with recursively expanding types simply will not compile (there is a `hir_analysis_recursive_generic_parameter` for that). closes rust-lang/rust#143241 2025-07-28T14:54:53+00:00 Cameron Steffen cam.steffen94@gmail.com 2025-07-25T00:09:05+00:00 urn:sha1:b43164cef643957f9e1cd20dffdbb736f3f3c298 2025-07-28T08:50:59+00:00 bors bors@rust-lang.org 2025-07-28T08:50:59+00:00 urn:sha1:65b6cdb6a6d33987b9d642a4882283c71fbe3957 Rollup of 7 pull requests Successful merges: - rust-lang/rust#144072 (update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs) - rust-lang/rust#144151 (`tests/ui/issues/`: The Issues Strike Back [1/N]) - rust-lang/rust#144300 (Clippy fixes for miropt-test-tools) - rust-lang/rust#144399 (Add a ratchet for moving all standard library tests to separate packages) - rust-lang/rust#144472 (str: Mark unstable `round_char_boundary` feature functions as const) - rust-lang/rust#144503 (Various refactors to the codegen coordinator code (part 3)) - rust-lang/rust#144530 (coverage: Infer `instances_used` from `pgo_func_name_var_map`) r? `@ghost` `@rustbot` modify labels: rollup 2025-07-28T06:36:54+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-07-28T06:36:54+00:00 urn:sha1:c462895a6f0b463ff0c1c1db2a3a654d7e5976c7 coverage: Infer `instances_used` from `pgo_func_name_var_map` In obscure circumstances involving macro-expanded spans, we would sometimes emit a covfun record for a function with no physical coverage counters, and therefore no corresponding entry in the “PGO names” section of the binary. The absence of that name entry causes `llvm-cov` to fail with the cryptic error message: ```text malformed instrumentation profile data: function name is empty ``` We can eliminate this mismatch by removing `instances_used` entirely, and instead inferring its contents from the keys of `pgo_func_name_var_map`. This makes it impossible for a "used" function to lack a PGO name entry. --- This is an attempt to eliminate the cause of rust-lang/rust#141577 when re-landing changes like rust-lang/rust#144298 in the future. I haven't been able to reproduce the underlying issue in an in-tree test, because the only known repro involves a non-trivial derive proc-macro that relies on `syn` and `proc-macro2`. But I have manually verified in a separate branch that this change would have prevented the reoccurrence of https://github.com/rust-lang/rust/issues/141577#issuecomment-3120667286. 2025-07-28T06:36:54+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-07-28T06:36:54+00:00 urn:sha1:ec86930c1d909b8114ce055c69746ca2c84b2ef4 Various refactors to the codegen coordinator code (part 3) Continuing from https://github.com/rust-lang/rust/pull/144062 this removes an option without any known users, uses the object crate in favor of LLVM for getting the LTO bitcode and improves the coordinator channel handling.