diff options
| author | bors <bors@rust-lang.org> | 2024-12-05 04:16:03 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-12-05 04:16:03 +0000 |
| commit | 5a0a5e6db9727917ce3e36950dae92696bc17079 (patch) | |
| tree | 05f42624f96364959d87bec28365951a209a858e /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | acabb5248231987ae1f0c215208d1005a5db402d (diff) | |
| parent | 988f28d442d2e959897e43a239f67d42e0297990 (diff) | |
| download | rust-5a0a5e6db9727917ce3e36950dae92696bc17079.tar.gz rust-5a0a5e6db9727917ce3e36950dae92696bc17079.zip | |
Auto merge of #133828 - compiler-errors:incr-sad, r=lcnr
Make sure to record deps from cached task in new solver on first run We weren't actually performing a read of the dep node in `with_cached_task` in the new solver, which meant that all queries that computed a goal for the first time were just not recording the query dependencies that we call in that query. In the incremental test, the typeck query for `fn poll` isn't being marked red even tho it's invalidated due to its writeback results changing. This happens b/c we normalize `Self::Error` into `Error`, which should call `type_of` which is a red query (since `ty::Adt` contains an `AdtDef`, and that `AdtDef`'s stable hash changes since it's ). However, since we weren't tracking deps in that normalize query, the typeck result was remaining green, and we were trying to decode a def id that no longer exists (the field that got removed). r? lcnr
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
