diff options
| author | bors <bors@rust-lang.org> | 2023-11-27 10:22:08 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-27 10:22:08 +0000 |
| commit | b29a1e00f850e548f3021ea523d0e143724fa9b7 (patch) | |
| tree | 8c0f267206774bbf92e9952863f0d4628a1d0653 /tests/ui/consts/std/alloc.rs | |
| parent | cc1130732d1b246d1bb11890a063878f68ebb0f5 (diff) | |
| parent | 4f1cf0b5dad1ae8d791b33e9112ed8c4cb61788a (diff) | |
| download | rust-b29a1e00f850e548f3021ea523d0e143724fa9b7.tar.gz rust-b29a1e00f850e548f3021ea523d0e143724fa9b7.zip | |
Auto merge of #118352 - Zalathar:llvm-hash, r=onur-ozkan
bootstrap: Memoize the LLVM rebuild hash to avoid very slow `x check` Recently I've encountered a massive regression in the performance of re-running `x check` after making no changes. It used to take around 2 seconds, and now it takes 20-30 seconds. That's quite a hassle when r-a runs it every time I save. After some poking around, what I've found is that each individual call to `generate_smart_stamp_hash` doesn't take a particularly long time (around 0.5 sec), but it gets called dozens of times during `x check`, and that seems to be what's adding up to 20-30 seconds. --- https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Massive.20regression.20in.20no-op.20.60x.20check.60 cc `@onur-ozkan`
Diffstat (limited to 'tests/ui/consts/std/alloc.rs')
0 files changed, 0 insertions, 0 deletions