Rework lint pass running#158239
Conversation
It's a bad name: long, and contains a negative. `skippable_lints` is better.
In particular, `late_lint_mod` doesn't filter consistently: it only checks if `builtin_lints` needs running in the `passes.is_empty()` case, and it doesn't check if the other passes need running at all.
It's called in two cases: pre-expansion lists, and early lints. The appropriate builtin pass is specified at the call site but the appropriate other passes are chosen within, which is inconsistent. This commit changes it so everything is chosen within, based on the boolean `pre_expansion_lint` parameter. `check_ast_node_inner` is split into `run_passes` and `run_pass`; the extra function is needed because the genericness of `builtin_lints` is pushed down one level below `check_ast_node`.
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt
cc @rust-lang/clippy |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Rework lint pass running
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (9309619): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -3.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -3.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 512.761s -> 504.991s (-1.52%) |
|
I have added a new commit renaming |
This comment has been minimized.
This comment has been minimized.
09591e3 to
2724e23
Compare
|
@bors r+ |
|
@bors p=6 threading between rollups |
|
💔 Test for e70076a failed: CI. Failed job:
|
|
no apparent cause @bors retry |
This comment has been minimized.
This comment has been minimized.
Rework lint pass running Some cleanups relating to the running of lint passes. r? @Urgau
|
💔 Test for 6913ee1 failed: CI. Failed jobs:
|
|
@bors retry |
|
Giving this a shot while I figure out the rollup situation @bors p=5 |
This comment has been minimized.
This comment has been minimized.
Rework lint pass running Some cleanups relating to the running of lint passes. r? @Urgau
|
💔 Test for e04e764 failed: CI. Failed job:
|
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
@bors p=6 |
|
⌛ Testing commit 2724e23 with merge a9a3722... Workflow: https://github.com/rust-lang/rust/actions/runs/28070770324 |
Rework lint pass running Some cleanups relating to the running of lint passes. r? @Urgau
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
❗ You can only retry pull requests that are approved and have a previously failed auto build. Hint: There is currently a pending auto build on this PR. To cancel it, run |
|
Ugh rust-log-analyzer fooled me again |
View all comments
Some cleanups relating to the running of lint passes.
r? @Urgau