diff options
| author | bors <bors@rust-lang.org> | 2023-04-23 15:41:45 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-04-23 15:41:45 +0000 |
| commit | 915aa06700af4a2363639bae70201cd7387470ad (patch) | |
| tree | bf009fdf0aa6ba968eb11a0c5a2f1813f6c1e42a /tests/rustdoc-js-std/parser-errors.js | |
| parent | 3462f79e94f466a56ddaccfcdd3a3d44dd1dda9f (diff) | |
| parent | 173845ce0e4d2ae1c9f809caae352b6da5f339ce (diff) | |
| download | rust-915aa06700af4a2363639bae70201cd7387470ad.tar.gz | |
Auto merge of #110705 - saethlin:ignore-locals-cost, r=cjgillot
Remove the size of locals heuristic in MIR inlining
This heuristic doesn't necessarily correlate to complexity of the MIR Body. In particular, a lot of straight-line code in MIR tends to never reuse a local, even though any optimizer would effectively reuse the storage or just put everything in registers. So it doesn't even necessarily make sense that this would be a stack size heuristic.
So... what happens if we just delete the heuristic? The benchmark suite improves significantly. Less heuristics better?
r? `@cjgillot`
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions