rust/compiler/rustc_mir_transform/src/coverage, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-16T13:51:18+00:00Port `#[coverage]` to the new attribute system2025-07-16T13:51:18+00:00Sasha Pourcelotsasha.pourcelot@protonmail.com2025-07-13T09:51:22+00:00urn:sha1:4e054fc4c4809a3c1df60ea99077f4d662b79750mir: Use the `new` method for `BasicBlockData`2025-06-29T12:39:13+00:00dianqkdianqk@dianqk.net2025-06-16T14:31:25+00:00urn:sha1:24e553e6bcfa329b04b93c0978e00b492224a255mir: Add a `new` method to `statement`2025-06-29T12:13:36+00:00dianqkdianqk@dianqk.net2025-06-08T07:30:18+00:00urn:sha1:9f9cd5e2837f57504b92b5acbadb48ff0cb9e29c
Avoid introducing a large number of changes when adding optional initialization fields.
coverage: Revert "unused local file IDs" due to empty function names2025-05-27T13:33:29+00:00ZalatharZalathar@users.noreply.github.com2025-05-27T13:25:57+00:00urn:sha1:3f526eeec4efe8a31154b7b20b64d99c1badce9e
This reverts commit 3b22c21dd8c30f499051fe7a758ca0e5d81eb638, reversing
changes made to 5f292eea6d63abbd26f1e6e00a0b8cf21d828d7d.
coverage: Enlarge empty spans during MIR instrumentation, not codegen2025-05-09T14:24:01+00:00ZalatharZalathar@users.noreply.github.com2025-05-04T04:09:52+00:00urn:sha1:339556eb026e6d1a0a18313f9c3cfe0ab87fe738
This allows us to assume that coverage spans will only be discarded during
codegen in very unusual situations.
coverage: Handle hole spans without dividing spans into buckets2025-05-06T10:42:40+00:00ZalatharZalathar@users.noreply.github.com2025-04-17T07:03:08+00:00urn:sha1:77a7ae4e9fcbf3be3988c98015d7f52137bb237c
Because we no longer merge non-adjacent spans, there is no need to use buckets
to prevent merging across hole spans.
coverage: Only merge adjacent coverage spans2025-05-06T10:42:25+00:00ZalatharZalathar@users.noreply.github.com2025-04-12T07:52:55+00:00urn:sha1:4d5a1acebfe031ca2af75786295a2cd2a0633943
This also removes some manipulation of the function signature span that only
made sense in the context of merging non-adjacent spans.
Auto merge of #140288 - Zalathar:new-executor, r=jieyouxu2025-04-26T22:33:56+00:00borsbors@rust-lang.org2025-04-26T22:33:56+00:00urn:sha1:43e62a789c772642f79086f2cceef171cff30e63
compiletest: Re-land using the new non-libtest executor by default
This PR re-lands #139998, which had the misfortune of triggering download-rustc in its CI jobs, so we didn't get proper test metrics for comparison with the old implementation. So that was PR was reverted in #140233, with the intention of re-landing it alongside a dummy compiler change to inhibit download-rustc.
---
Original PR description for #139998:
>The new executor was implemented in #139660, but required a manual opt-in. This PR activates the new executor by default, but leaves the old libtest-based executor in place (temporarily) to make reverting easier if something unexpectedly goes horribly wrong.
>
>Currently the new executor can be explicitly disabled by passing the `-N` flag to compiletest (e.g. `./x test ui -- -N`), but eventually that flag will be removed, alongside the removal of the libtest dependency. The flag is mostly there to make manual comparative testing easier if something does go wrong.
>
>As before, there *should* be no user-visible difference between the old executor and the new executor.
---
r? jieyouxu
Trivial compiler change to inhibit download-rustc in CI2025-04-25T10:41:50+00:00ZalatharZalathar@users.noreply.github.com2025-04-25T10:41:50+00:00urn:sha1:1670de40e070e66e8074e1d534fd4acfa72acc39Trivial compiler change to inhibit download-rustc in CI2025-04-24T09:44:13+00:00ZalatharZalathar@users.noreply.github.com2025-04-24T09:44:13+00:00urn:sha1:f673c9b056741da5c40b8654a95c02115ab628ed