rust/compiler/rustc_codegen_llvm/src/coverageinfo, branch 1.78.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.78.02024-03-14T06:19:02+00:00coverage: Include recorded branch info in coverage instrumentation2024-03-14T06:19:02+00:00ZalatharZalathar@users.noreply.github.com2023-11-16T06:48:23+00:00urn:sha1:31d0b5017857cef35031a7d4210bd045758dcae2coverage: Add `CoverageKind::BlockMarker`2024-03-13T09:43:35+00:00ZalatharZalathar@users.noreply.github.com2024-02-08T01:39:15+00:00urn:sha1:c921ab17134a7e526ec9df3942890f5b501addcbcoverage: Remove all unstable values of `-Cinstrument-coverage`2024-03-13T00:14:09+00:00ZalatharZalathar@users.noreply.github.com2024-03-12T01:30:33+00:00urn:sha1:1f544ce305bc207c9d0539938219caf01ea230c9avoid collecting into vecs in some places2024-03-02T13:18:47+00:00Matthias Krügermatthias.krueger@famsik.de2024-03-02T13:18:47+00:00urn:sha1:7a48987006c1d69cb59fc253bbe2ad097af82645clean up potential_query_instability with FxIndexMap and UnordMap2024-02-14T10:36:37+00:00yukangmoorekang@gmail.com2024-02-11T11:50:50+00:00urn:sha1:3f27e4b3ea35c87c1e8a6b9b8a3c7e122f6299deadd missing potential_query_instability for keys and values in hashmap2024-01-30T04:43:10+00:00yukangmoorekang@gmail.com2024-01-30T04:42:29+00:00urn:sha1:ad526d831e295facc198610a27350076aa5aa438coverage: Add enums to accommodate other kinds of coverage mappings2024-01-11T05:43:12+00:00ZalatharZalathar@users.noreply.github.com2023-12-28T03:07:18+00:00urn:sha1:124fff0777014323be34f0a990c78c5cfe9f40dbcoverage: Avoid a query stability hazard in `function_coverage_map`2024-01-02T11:57:04+00:00ZalatharZalathar@users.noreply.github.com2024-01-02T11:57:04+00:00urn:sha1:5e7c1b93ac7f5fb1bd5297980e8b6b3657a10c32
When #118865 started enforcing the `rustc::potential_query_instability` lint in
`rustc_codegen_llvm`, it added an exemption for this site, arguing that the
entries are only used to create a list of filenames that is later sorted.
However, the list of entries also gets traversed when creating the function
coverage records in LLVM IR, which may be sensitive to hash-based ordering.
This patch therefore changes `function_coverage_map` to use `FxIndexMap`, which
should avoid hash-based instability by iterating in insertion order.
coverage: Avoid creating `func_coverage` for marker statements2023-12-16T00:10:11+00:00ZalatharZalathar@users.noreply.github.com2023-12-12T02:49:19+00:00urn:sha1:c57f28bbf75572e10c6165c33a2aef922315fdb4
Coverage marker statements should have no effect on codegen, but in some cases
they could have the side-effect of creating a `func_coverage` entry for their
enclosing function. That can lead to an ICE for functions that don't actually
have any coverage spans.
rustc_codegen_llvm: Enforce `rustc::potential_query_instability` lint2023-12-12T12:16:14+00:00Martin Nordholtsmartin.nordholts@codetale.se2023-12-12T12:14:53+00:00urn:sha1:f44ccbab2bbdc538b739d6a1f5f9fbdb8339f8f8
Stop allowing `rustc::potential_query_instability` on all of
`rustc_codegen_llvm` and instead allow it on a case-by-case basis. In
this case, both instances are safe to allow.