diff options
| author | León Orell Valerian Liehr <me@fmease.dev> | 2024-01-03 16:08:32 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-03 16:08:32 +0100 |
| commit | ea39f19fab548899410016edd8c1e4d8bff9012a (patch) | |
| tree | 969afe14cad6cd9e5d319030c8f438cc88acec48 /compiler/rustc_pattern_analysis/src | |
| parent | c2debecf98dec1bc79879e8074bfbc5c4293eea5 (diff) | |
| parent | 5e7c1b93ac7f5fb1bd5297980e8b6b3657a10c32 (diff) | |
| download | rust-ea39f19fab548899410016edd8c1e4d8bff9012a.tar.gz rust-ea39f19fab548899410016edd8c1e4d8bff9012a.zip | |
Rollup merge of #119514 - Zalathar:query-stability, r=wesleywiser
coverage: Avoid a query stability hazard in `function_coverage_map` 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. cc ``@Enselic``
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions