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.

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

Already on GitHub? Sign in to your account

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

Merged
merged 5 commits into from
Jul 8, 2017

Commits on Jul 7, 2017

  1. Configuration menu
    Copy the full SHA
    23f7092 View commit details
    Browse the repository at this point in the history
  2. Force specialization in number of varargs in key places

    This greatly reduces the cost of failure-to-inline
    timholy committed Jul 7, 2017
    Configuration menu
    Copy the full SHA
    4564726 View commit details
    Browse the repository at this point in the history
  3. More inlining prevention

    timholy committed Jul 7, 2017
    Configuration menu
    Copy the full SHA
    705a187 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    d702605 View commit details
    Browse the repository at this point in the history
  5. 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.
    timholy committed Jul 7, 2017
    Configuration menu
    Copy the full SHA
    7de02a3 View commit details
    Browse the repository at this point in the history