Try inlining trivial functions used by CTFE

[tmiasko]

r? @ghost

[tmiasko]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

[bors]

⌛ Trying commit 20982b3 with merge 4a69f8e80de4c2a2c4efdfa2ec39d3d688deaf31...

[bors]

☀️ Try build successful - checks-actions
Build commit: 4a69f8e80de4c2a2c4efdfa2ec39d3d688deaf31 (4a69f8e80de4c2a2c4efdfa2ec39d3d688deaf31)

[rust-timer]

Queued 4a69f8e80de4c2a2c4efdfa2ec39d3d688deaf31 with parent 613ef74, future comparison URL.

@rustbot label: +S-waiting-on-perf

[rust-timer]

Finished benchmarking try commit (4a69f8e80de4c2a2c4efdfa2ec39d3d688deaf31): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[tmiasko]

The change was targeting the ctfe-stress-4 benchmark. The full wall times show consistent improvements of -5.0%, as do incr-full runs. The detailed comparisons show improvements in eval_to_allocation_raw query as intended. All of those results are essentially at the lower end of historical results, but not particularly significant.

r? @oli-obk

[oli-obk]

@bors r+

[bors]

📌 Commit 20982b3 has been approved by oli-obk

[bors]

⌛ Testing commit 20982b3 with merge bf193d6...

[bors]

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing bf193d6 to master...