diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-12-29 11:19:28 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-29 11:19:28 +0100 |
| commit | 4b9a76cddf26531c4824b5e3016f6b8332573088 (patch) | |
| tree | 7385feecbf47a41e764c35364930ef95975a4c33 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 12ad77722182bf5ea01092115e26edb9f634a4eb (diff) | |
| parent | 8529b63e2bc1afd6cefdf204e6b576b98394371c (diff) | |
| download | rust-4b9a76cddf26531c4824b5e3016f6b8332573088.tar.gz rust-4b9a76cddf26531c4824b5e3016f6b8332573088.zip | |
Rollup merge of #119401 - Zalathar:query-stability, r=Nilstrieb
coverage: Avoid a possible query stability hazard in `CoverageCounters` #119252 revealed a possible query stability hazard in `CoverageCounters`: we iterate over the entries of an `FxHashMap` in a way that allows the iteration order to potentially affect the relative creation order of MIR blocks. I'm not sure whether there's an actual stability problem or not in practice, but it's certainly a hazard, and I don't see any reason not to switch over to `FxIndexMap` to avoid potential issues. --- This can either be merged on its own, or incorporated into #119252. cc `@Enselic` r? `@cjgillot`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions