rust/tests/coverage/condition, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2025-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: Shrink call spans to just the function name2025-04-01T02:07:33+00:00ZalatharZalathar@users.noreply.github.com2025-03-29T10:33:01+00:00urn:sha1:577272eedeaace00aa695135b3b8fee3768536a5
This is a way to shrink call spans that doesn't involve mixing different spans,
and avoids overlap with argument spans.
This patch also removes some low-value comments that were causing rustfmt to
ignore the match arms.
Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, r=wesleywiser"2024-12-23T01:30:37+00:00ZalatharZalathar@users.noreply.github.com2024-12-22T03:26:54+00:00urn:sha1:87c2f9a5be900e835f3c41cec2886d54ec0ca012
This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing
changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
Stabilize #[coverage] attribute2024-12-17T02:07:06+00:00ltdkusr@ltdk.xyz2024-09-23T23:40:22+00:00urn:sha1:cb487cc2fa3c5ebfddd22d6721cf1669943c1774coverage: 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.)
coverage: Instrument the RHS value of lazy logical operators2024-05-30T05:38:46+00:00ZalatharZalathar@users.noreply.github.com2024-05-01T07:33:33+00:00urn:sha1:35a8746832a4d9103f317c5cac56cfa1e0316d8c
When a lazy logical operator (`&&` or `||`) occurs outside of an `if`
condition, it normally doesn't have any associated control-flow branch, so we
don't have an existing way to track whether it was true or false.
This patch adds special code to handle this case, by inserting extra MIR blocks
in a diamond shape after evaluating the RHS. This gives us a place to insert
the appropriate marker statements, which can then be given their own counters.
coverage: Add a test for `-Zcoverage-options=condition`2024-05-30T05:38:46+00:00Dorian Péronperon@adacore.com2024-04-29T15:58:14+00:00urn:sha1:20174e6638eb0d5ac0195706ce6cc7185949a407