rust/compiler/rustc_codegen_llvm/src/coverageinfo, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2025-07-30T03:17:05+00:00coverage: 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.
Revert "coverage: Enlarge empty spans during MIR instrumentation, not codegen"2025-07-26T01:14:40+00:00ZalatharZalathar@users.noreply.github.com2025-07-26T01:14:40+00:00urn:sha1:2b17897092443d3873e273dfa6366784b78f5b44
This reverts commit f877aa7d14916f71a2f88c6d4c009e7ded7684c4.
coverage: Enlarge empty spans during MIR instrumentation, not codegen2025-07-22T09:49:54+00:00ZalatharZalathar@users.noreply.github.com2025-05-04T04:09:52+00:00urn:sha1:f877aa7d14916f71a2f88c6d4c009e7ded7684c4
This allows us to assume that coverage spans will only be discarded during
codegen in very unusual situations.
Remove methods from StaticCodegenMethods that are not called in cg_ssa itself2025-05-28T20:55:00+00:00bjorn317426603+bjorn3@users.noreply.github.com2025-01-09T18:29:05+00:00urn:sha1:d7c0bde0c11301b9a782eabc469f7a7548505d4fRemove a couple of uses of interior mutability around statics2025-05-28T20:55:00+00:00bjorn317426603+bjorn3@users.noreply.github.com2024-12-13T09:52:38+00:00urn:sha1:0fd257d66ca761c5eba965fac52acffe3a8a7d96coverage: Revert "unused local file IDs" due to empty function names2025-05-27T13:33:29+00:00ZalatharZalathar@users.noreply.github.com2025-05-27T13:25:57+00:00urn:sha1:3f526eeec4efe8a31154b7b20b64d99c1badce9e
This reverts commit 3b22c21dd8c30f499051fe7a758ca0e5d81eb638, reversing
changes made to 5f292eea6d63abbd26f1e6e00a0b8cf21d828d7d.
coverage: Detect unused local file IDs to avoid an LLVM assertion2025-05-09T14:24:03+00:00ZalatharZalathar@users.noreply.github.com2025-05-09T10:57:17+00:00urn:sha1:078144fdfa7ae627d43cd919d660a71bef1e4658
This case can't actually happen yet (other than via a testing flag), because
currently all of a function's spans must belong to the same file and expansion.
But this will be an important edge case when adding expansion region support.
coverage: Hoist `counter_for_bcb` out of its loop2025-05-09T14:24:03+00:00ZalatharZalathar@users.noreply.github.com2025-05-09T11:27:27+00:00urn:sha1:8cd8b23b9e4b1f05373831644b005b21a13a9c69
Having this helper function in the loop was confusing, because it doesn't rely
on anything that changes between loop iterations.