rust/tests/coverage/macro_name_span.cov-map, branch cargo_update https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=cargo_update 2025-05-06T10:42:25+00:00 coverage: Only merge adjacent coverage spans 2025-05-06T10:42:25+00:00 Zalathar Zalathar@users.noreply.github.com 2025-04-12T07:52:55+00:00 urn: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:00 Zalathar Zalathar@users.noreply.github.com 2025-04-24T07:36:50+00:00 urn:sha1:c53a76743c01afa356ae5301bc1b35044354da7a coverage: Don't split bang-macro spans, just truncate them 2025-04-01T02:13:21+00:00 Zalathar Zalathar@users.noreply.github.com 2025-03-25T11:02:22+00:00 urn:sha1:26cea8a2863a3aa0fd169d8561ce77036ef6983e coverage: Include the highest counter ID seen in `.cov-map` dumps 2024-10-11T10:04:37+00:00 Zalathar Zalathar@users.noreply.github.com 2024-10-08T02:13:05+00:00 urn: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: Discard spans that fill the entire function body 2024-02-15T23:57:03+00:00 Zalathar Zalathar@users.noreply.github.com 2024-02-15T07:12:27+00:00 urn:sha1:cd9021e8cb1ab6cf5bdf341d7e0538703d86fc5b When we try to extract coverage-relevant spans from MIR, sometimes we see MIR statements/terminators whose spans cover the entire function body. Those spans tend to be unhelpful for coverage purposes, because they often represent compiler-inserted code, e.g. the implicit return value of `()`. macro_rules: Less hacky heuristic for using `tt` metavariable spans 2024-01-04T00:53:56+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2023-12-01T15:23:16+00:00 urn:sha1:e1d12c8caf4c3dad0a28c88e5d454a3eb6e1f955 coverage: Regression test for #117788 2023-11-13T01:31:44+00:00 Zalathar Zalathar@users.noreply.github.com 2023-11-13T00:33:44+00:00 urn:sha1:514e324c32db0790a13f52a96e230663f3fe0525 Without the workaround applied, this test will produce malformed mappings that cause `llvm-cov` to fail. (And if it does emit well-formed mappings, they should be obviously incorrect.)