diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-03-18 12:04:21 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-18 12:04:21 +0100 |
| commit | 7ebf2cd2b8f1f8c11f9339ef337d336a91d6f7dc (patch) | |
| tree | 599c1fff28765ed61a3acb84485935c9c2417d04 /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | 9599f3cc5430039b615bc5171be41a6733083dc0 (diff) | |
| parent | 675c4aa2c1c142415d4e95bf550ec0b1de2493d0 (diff) | |
| download | rust-7ebf2cd2b8f1f8c11f9339ef337d336a91d6f7dc.tar.gz rust-7ebf2cd2b8f1f8c11f9339ef337d336a91d6f7dc.zip | |
Rollup merge of #108772 - jyn514:faster-tidy, r=the8472
Speed up tidy quite a lot I highly recommend reviewing this commit-by-commit. Based on #106440 for convenience. ## Timings These were collected by running `x test tidy -v` to copy paste the command, then using [`samply record`](https://github.com/mstange/samply). before (8 threads)  after (8 threads)  before (64 threads)  after (64 threads)  The last commit makes tidy use more threads, so comparing "before (8 threads)" to "after (64 threads)" is IMO the most realistic comparison. Locally, that brings the time for me to run tidy down from 4 to .9 seconds, i.e. the majority of the time for `x test tidy` is now spend running `fmt --check`. r? `@the8472`
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions