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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Optimize mk_region #108020

Merged
merged 4 commits into from
Feb 16, 2023
Merged

Optimize mk_region #108020

merged 4 commits into from
Feb 16, 2023

Commits on Feb 14, 2023

  1. Remove reuse_or_mk_region. 

    It's not used on any hot paths, and so has little perf benefit, and it
interferes with the optimizations in the following commits.
    @nnethercote
    nnethercote committed Feb 14, 2023
    Configuration menu
    Copy the full SHA
    7439028 View commit details
    Browse the repository at this point in the history

  2. Add specialized variants of mk_region. 

    Much like there are specialized variants of `mk_ty`. This will enable
some optimization in the next commit.

Also rename the existing `re_error*` functions as `mk_re_error*`, for
consistency.
    @nnethercote
    nnethercote committed Feb 14, 2023
    Configuration menu
    Copy the full SHA
    cef9004 View commit details
    Browse the repository at this point in the history

  3. Pre-intern some ReVars and ReLateBounds.

    @nnethercote
    nnethercote committed Feb 14, 2023
    Configuration menu
    Copy the full SHA
    a4d3c9a View commit details
    Browse the repository at this point in the history

  4. Replace an unnecessary mk_ty call with mk_array.

    @nnethercote
    nnethercote committed Feb 14, 2023
    Configuration menu
    Copy the full SHA
    9a53cee View commit details
    Browse the repository at this point in the history