rust/src/tools/coverage-dump, branch 1.90.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.90.02025-05-10T16:35:20+00:00Update miniz_oxide dependency of coverage_dump2025-05-10T16:35:20+00:00oyvindlnoyvindln@users.noreply.github.com2025-05-10T16:35:20+00:00urn:sha1:5bd3d0e99da2d79cafd73e7f174b99fe8349fa75coverage-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-dump: Make filenames available to covfun record dumping2025-05-06T01:58:58+00:00ZalatharZalathar@users.noreply.github.com2025-04-24T03:47:13+00:00urn:sha1:041b2b2c982edb6e36a7d80081d040dbaf388a2b
Actually printing the filenames is deferred to a subsequent commit that will
simultaneously bless all affected tests.
coverage-dump: Include filenames hash in covfun line data2025-05-06T01:58:58+00:00ZalatharZalathar@users.noreply.github.com2025-04-22T11:49:57+00:00urn:sha1:f1b8cd433f31af7e25fb8b7ec7436d6ebf3f5410coverage-dump: Extract a common parser method for maybe-compressed bytes2025-05-06T01:58:58+00:00ZalatharZalathar@users.noreply.github.com2025-04-23T07:47:01+00:00urn:sha1:bc3f0e326a5ef77bb4e3531db5190109d8e2420bcoverage-dump: Extract some common code to an `llvm_utils` submodule2025-05-06T01:58:50+00:00ZalatharZalathar@users.noreply.github.com2025-04-23T07:36:01+00:00urn:sha1:89319f2e128379a96943de2be347ec09a80abca4bootstrap: Add check/test/run steps for src/tools/coverage-dump2025-05-06T01:48:37+00:00ZalatharZalathar@users.noreply.github.com2025-04-22T06:30:48+00:00urn:sha1:a3d5562fcf7f67491d55588ac3279bfade9dadcd
This also causes the coverage-dump unit tests to run in CI and `./x test` by
default.
Rustfmt2025-02-08T22:12:13+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-02-08T22:12:13+00:00urn:sha1:1fcae03369abb4c2cc180cd5a49e1f4440a81300coverage: 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.)
Reformat using the new identifier sorting from rustfmt2024-09-22T23:11:29+00:00Michael Gouletmichael@errs.io2024-09-22T23:05:04+00:00urn:sha1:c682aa162b0d41e21cc6748f4fecfe01efb69d1f