rust/compiler/rustc_middle/src/mir/coverage.rs, branch cargo_updatehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=cargo_update2025-08-06T12:38:52+00:00coverage: Remove all unstable support for MC/DC instrumentation2025-08-06T12:38:52+00:00ZalatharZalathar@users.noreply.github.com2025-08-06T12:02:01+00:00urn:sha1:81ed042c8cc4a1bd677c9209cf9edca6b91af04acoverage: Don't store a body span in `FunctionCoverageInfo`2025-03-18T12:18:24+00:00ZalatharZalathar@users.noreply.github.com2025-03-18T10:19:08+00:00urn:sha1:cc8336b6c1c5400cf85521218afda47dbbbe782ccoverage: Remove the old code for simplifying counters after MIR opts2025-02-06T10:44:31+00:00ZalatharZalathar@users.noreply.github.com2025-01-25T07:41:35+00:00urn:sha1:bd855b6c9efc25a9f1eba3febd3d04f1b23a1ec5coverage: Defer part of counter-creation until codegen2025-02-06T10:44:31+00:00ZalatharZalathar@users.noreply.github.com2025-01-22T02:55:08+00:00urn:sha1:20d051ec870739c8f263e5f6f581ca24a5dd56fdcoverage: Store BCB node IDs in mappings, and resolve them in codegen2025-02-06T10:44:29+00:00ZalatharZalathar@users.noreply.github.com2025-01-20T11:43:59+00:00urn:sha1:ee7dc06cf181c073b1040669a40bc325d00f8c6d
Even though the coverage graph itself is no longer available during codegen,
its nodes can still be used as opaque IDs.
Exclude `mir::coverage` types from TypeFoldable/TypeVisitable2025-01-24T05:06:18+00:00ZalatharZalathar@users.noreply.github.com2025-01-22T09:35:33+00:00urn:sha1:8a6e06fecb4feea56b97e181e3ff93a7a3bea8d6
These types are unlikely to ever contain type information in the foreseeable
future, so excluding them from TypeFoldable/TypeVisitable avoids some unhelpful
derive boilerplate.
coverage: Remove `BcbCounter` and `BcbExpression`2025-01-18T11:14:16+00:00ZalatharZalathar@users.noreply.github.com2025-01-17T10:34:57+00:00urn:sha1:6000d5c462b767e3c5871034824964d0b0897a26
Making these separate types from `CovTerm` and `Expression` was historically
very helpful, but now that most of the counter-creation work is handled by
`node_flow` they are no longer needed.
rename `BitSet` to `DenseBitSet`2025-01-11T11:34:01+00:00Rémy Rakicremy.rakic+github@gmail.com2025-01-07T15:19:05+00:00urn:sha1:a13354bea05968799a5be5521691322274fa6a9e
This should make it clearer that this bitset is dense, with the
advantages and disadvantages that it entails.
coverage: Store coverage source regions as `Span` until codegen2024-12-19T07:09:09+00:00ZalatharZalathar@users.noreply.github.com2024-12-18T10:00:51+00:00urn:sha1:34ed51cb837d1dd755b9b97798a41c8cd0358ca6coverage: Use a query to find counters/expressions that must be zero2024-12-08T09:53:39+00:00ZalatharZalathar@users.noreply.github.com2024-12-06T11:33:24+00:00urn:sha1:2022ef7f12fe6ebc810ee5731557d23ba763cc96
This query (`coverage_ids_info`) already determines which counter/expression
IDs are unused, so it only takes a little extra effort to also determine which
counters/expressions must have a value of zero.