diff options
| author | bors <bors@rust-lang.org> | 2023-04-17 02:36:38 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-04-17 02:36:38 +0000 |
| commit | 5546cb64f6fbba70529582bbe58a40ba4a8ed9fc (patch) | |
| tree | 82603ce3d07dc6bb247669285f38009495a80d85 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 23eb90ffa77943153d203c3d184c182490d758e7 (diff) | |
| parent | 354177504757c3b79e38daa3f6c81004470f455f (diff) | |
| download | rust-5546cb64f6fbba70529582bbe58a40ba4a8ed9fc.tar.gz | |
Auto merge of #109247 - saethlin:inline-without-inline, r=oli-obk
Permit MIR inlining without #[inline]
I noticed that there are at least a handful of portable-simd functions that have no `#[inline]` but compile to an assign + return.
I locally benchmarked inlining thresholds between 0 and 50 in increments of 5, and 50 seems to be the best. Interesting. That didn't include check builds though, ~maybe perf will have something to say about that~.
Perf has little useful to say about this. We generally regress all the check builds, as best as I can tell, due to a number of small codegen changes in a particular hot function in the compiler. Probably this is because we've nudged the inlining outcomes all over, and uses of `#[inline(always)]`/`#[inline(never)]` might need to be adjusted.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions