https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp 2025-05-06T10:42:25+00:00 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. 2025-05-06T01:58:58+00:00 Zalathar Zalathar@users.noreply.github.com 2025-04-24T07:36:50+00:00 urn:sha1:c53a76743c01afa356ae5301bc1b35044354da7a 2024-11-08T09:43:08+00:00 Zalathar Zalathar@users.noreply.github.com 2024-11-05T10:59:10+00:00 urn:sha1:3c30fe3423b1e7d92584436493bd8fa6f17e13d0 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.) 2024-05-14T03:58:40+00:00 Zalathar Zalathar@users.noreply.github.com 2024-05-14T03:51:24+00:00 urn: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. 2023-11-07T00:15:19+00:00 Zalathar Zalathar@users.noreply.github.com 2023-11-01T10:28:53+00:00 urn:sha1:49127c64d6998526d9f723a653312d0cf5310454