rust/tests/coverage/try_error_result.cov-map, branch 1.87.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.87.02025-02-13T02:45:53+00:00coverage: Eliminate more counters by giving them to unreachable nodes2025-02-13T02:45:53+00:00ZalatharZalathar@users.noreply.github.com2025-02-11T03:09:11+00:00urn:sha1:ab786d3b98d640b1208eff371c1184e3e8ce1d17
When preparing a function's coverage counters and metadata during codegen, any
part of the original coverage graph that was removed by MIR optimizations can
be treated as having an execution count of zero.
Somewhat counter-intuitively, if we give those unreachable nodes a _higher_
priority for receiving physical counters (instead of counter expressions), that
ends up reducing the total number of physical counters needed.
This works because if a node is unreachable, we don't actually create a
physical counter for it. Instead that node gets a fixed zero counter, and any
other node that would have relied on that physical counter in its counter
expression can just ignore that term completely.
coverage: Completely overhaul counter assignment, using node-flow graphs2025-01-16T11:07:18+00:00ZalatharZalathar@users.noreply.github.com2025-01-12T10:36:07+00:00urn:sha1:f1300c860e6ff4e024f0a347b87f94e36785ce49coverage: Prefer to visit nodes whose predecessors have been visited2024-12-07T01:13:12+00:00ZalatharZalathar@users.noreply.github.com2024-12-05T07:57:17+00:00urn:sha1:ac815ff6b0c8f0fd68ddf666ea1f96e362c65300coverage: Add an extra "transcribe" step after counter creation2024-12-04T06:50:52+00:00ZalatharZalathar@users.noreply.github.com2024-11-29T01:58:35+00:00urn:sha1:44e4e4515c877093379e368b591b6aae3545f77ccoverage: 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.)
Create mapped places upon seeing them in the body.2024-07-13T11:54:25+00:00Camille GILLOTgillot.camille@gmail.com2024-06-27T14:51:58+00:00urn:sha1:76f5bc6a9ffcd0b3255b5266cc963635a12f6016Tweak various coverage test files for slightly nicer formatting2024-05-29T04:34:11+00:00ZalatharZalathar@users.noreply.github.com2024-05-29T04:06:53+00:00urn:sha1:448d63e9469c293c3855867d29cbff210691db92
For coverage tests, splitting code across multiple lines often makes the
resulting coverage report easier to interpret, so we force rustfmt to retain
line breaks by adding dummy line comments with `//`.
coverage: Simplify counter expressions using simple algebra2024-05-14T03:58:40+00:00ZalatharZalathar@users.noreply.github.com2024-05-14T03:51:24+00:00urn:sha1:d01df6f9aadf58a00357bd89b8fc25a44822ba77
Some of these cases currently don't occur in practice, but are included for
completeness, and to avoid having to add them later as branch coverage and
MC/DC coverage start building more complex expressions.
Enable by default.2024-02-09T21:13:51+00:00Camille GILLOTgillot.camille@gmail.com2023-01-18T17:57:50+00:00urn:sha1:e132cac3c45217f5f2b730ddd684fdd4700ffc4ccoverage: Add `#[rustfmt::skip]` to tests with non-standard formatting2024-01-16T04:56:37+00:00ZalatharZalathar@users.noreply.github.com2024-01-16T02:40:01+00:00urn:sha1:f1494425bbb68e71f2bf3aa215fb71978b36acf2
These tests deliberately use non-standard formatting, so that the line
execution counts reported by `llvm-cov` reveal additional information about
where code regions begin and end.