Repository navigation
Skip move checks when the size limit is zero - #164332
rust-bors[bot] merged 1 commit into
Conversation
|
r? @TaKO8Ki rustbot has assigned @TaKO8Ki. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@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.
…ks, r=<try> Skip move checks when the size limit is zero
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (b5c78cd): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @bors rollup=iffy rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)This perf run didn't have relevant results for this metric. CyclesResults (primary 2.4%, secondary 4.2%)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: 489.902s -> 487.199s (-0.55%) |
|
Thank you! @bors r+ rollup |
Rollup merge of #164332 - charliermarsh:charlie/skip-disabled-move-checks, r=TaKO8Ki Skip move checks when the size limit is zero ## Summary When the move-size limit is zero (i.e., the default), the individual large-assignment checks already return without doing anything. But we still traverse the reachable MIR blocks and monomorphize callee types before reaching those checks. This PR instead returns early from `check_moves`.
Summary
When the move-size limit is zero (i.e., the default), the individual large-assignment checks already return without doing anything. But we still traverse the reachable MIR blocks and monomorphize callee types before reaching those checks. This PR instead returns early from
check_moves.