rust/compiler/rustc_codegen_llvm/src/coverageinfo, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-09-16T12:00:10+00:00Mark some coverage-related bindings as safe2025-09-16T12:00:10+00:00ZalatharZalathar@users.noreply.github.com2025-09-16T11:44:40+00:00urn:sha1:06a7460455284aca27fbf65505c385e3dc275da3Stop using `as_c_char_ptr` for coverage-related bindings2025-09-16T11:36:45+00:00ZalatharZalathar@users.noreply.github.com2025-09-16T11:36:45+00:00urn:sha1:79c9f6ee9b3229279ffdaa0515c7b0320c0b0737coverage: Remove all unstable support for MC/DC instrumentation2025-08-06T12:38:52+00:00ZalatharZalathar@users.noreply.github.com2025-08-06T12:02:01+00:00urn:sha1:81ed042c8cc4a1bd677c9209cf9edca6b91af04acoverage: Represent `CovmapVersion` as an enum2025-08-04T03:48:41+00:00ZalatharZalathar@users.noreply.github.com2025-08-03T04:35:17+00:00urn:sha1:b37c214ec2bbb7609eb4b963bb2b0da160fef57f
Using an enum here was historically not worth the extra hassle, but now we can
lean on `#[derive(TryFromU32)]` to hide most of the boilerplate.
coverage: Simplify access to debug/testing `-Zcoverage-options` flags2025-08-04T03:48:41+00:00ZalatharZalathar@users.noreply.github.com2025-08-02T08:41:04+00:00urn:sha1:f496e83fe9a12cbaec6a61da83ba32159a87afdecoverage: Hoist `counter_for_bcb` out of its loop2025-08-04T01:55:40+00:00ZalatharZalathar@users.noreply.github.com2025-05-09T11:27:27+00:00urn:sha1:16843ce427965a39a5f226ce3057ba3c2f5ed23c
Having this helper function in the loop was confusing, because it doesn't rely
on anything that changes between loop iterations.
coverage: Include an `Instance` in `CovfunRecord` for debug messages2025-08-04T01:55:25+00:00ZalatharZalathar@users.noreply.github.com2025-08-02T12:17:14+00:00urn:sha1:33706fc17f858caf42d36a9f67ef794269b6a83fcoverage: Re-land "Enlarge empty spans during MIR instrumentation"2025-07-30T03:17:05+00:00ZalatharZalathar@users.noreply.github.com2025-05-04T04:09:52+00:00urn:sha1:2e6f4a59226fd82c526df0f61fefc6fea44e7750
This allows us to assume that coverage spans will only be discarded during
codegen in very unusual situations.
coverage: Clarify that getting a PGO name also makes a function "used"2025-07-27T11:49:46+00:00ZalatharZalathar@users.noreply.github.com2025-07-27T11:29:48+00:00urn:sha1:89b6b0b6a482cb0d632f54f14936def9c034570dcoverage: Infer `instances_used` from `pgo_func_name_var_map`2025-07-27T11:49:37+00:00ZalatharZalathar@users.noreply.github.com2025-07-27T11:19:07+00:00urn:sha1:24e2b4832bfa0bf1b60159af0ae11b15de55590e
In obscure circumstances, we would sometimes emit a covfun record for a
function with no physical coverage counters, causing `llvm-cov` to fail with
the cryptic error message:
malformed instrumentation profile data: function name is empty
We can eliminate this mismatch by removing `instances_used` entirely, and
instead inferring its contents from the keys of `pgo_func_name_var_map`.
This makes it impossible for a "used" function to lack a PGO name entry.