rust/tests/coverage/tight_inf_loop.cov-map, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-05-06T10:42:25+00:00coverage: 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.
coverage-dump: Dump filenames instead of global file IDs (and bless)2025-05-06T01:58:58+00:00ZalatharZalathar@users.noreply.github.com2025-04-24T07:36:50+00:00urn:sha1:c53a76743c01afa356ae5301bc1b35044354da7acoverage: Don't create counters for code that was removed by MIR opts2025-02-06T10:44:31+00:00ZalatharZalathar@users.noreply.github.com2025-01-25T07:24:02+00:00urn:sha1:bf1f254b13d09aedfd8b44611f39736c32d5d0f6coverage: Include the highest counter ID seen in `.cov-map` dumps2024-10-11T10:04:37+00:00ZalatharZalathar@users.noreply.github.com2024-10-08T02:13:05+00:00urn:sha1:599f95ecc26fb68cccbf79780dd1825a4cf73eb0
When making changes that have a large impact on coverage counter creation, this
makes it easier to see whether the number of physical counters has changed.
(The highest counter ID seen in coverage maps is not necessarily the same as
the number of physical counters actually used by the instrumented code, but
it's the best approximation we can get from looking only at the coverage maps,
and it should be reasonably accurate in most cases.)
coverage: Migrate `tests/coverage-map` into `tests/coverage`2023-11-07T00:15:19+00:00ZalatharZalathar@users.noreply.github.com2023-11-01T10:28:53+00:00urn:sha1:49127c64d6998526d9f723a653312d0cf5310454