Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide inline-worthiness based on a more nuanced cost model #22210

Merged
merged 5 commits into from
Jul 8, 2017
Merged

Decide inline-worthiness based on a more nuanced cost model #22210

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
23f7092
Protect some `throw`s with atsign-noinline
timholy Jun 7, 2017
4564726
Force specialization in number of varargs in key places
timholy Jun 7, 2017
705a187
More inlining prevention
timholy Jul 1, 2017
d702605
Work around penalty from splatting an Integer
timholy Jun 18, 2017
7de02a3
Decide inline-worthiness based on a more nuanced cost model
timholy Jul 7, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Decide inline-worthiness based on a more nuanced cost model 
This switches to a model in which we estimate the runtime of the
function; if it's fast, then we should inline it. The estimate of
runtime is extremely crude, and doesn't even take loops into account.
  • Loading branch information
@timholy
timholy committed Jul 7, 2017
commit 7de02a33f9c95178a8f5880dc39f0ced9d3c9e7b
Loading