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

inlining: avoid Union computations in the inliner call analysis #44095

Merged
merged 1 commit into from
Feb 13, 2022

Conversation

aviatesk
Copy link
Sponsor Member

@aviatesk aviatesk commented Feb 9, 2022

By reusing MethodMatch.fully_covers information.
I think this logic would be valid if the analysis accounts for "no method error" (corresponding to the length(meth) == 0 cases).

@aviatesk aviatesk requested a review from vtjnash February 9, 2022 17:00
@vtjnash
Copy link
Sponsor Member

vtjnash commented Feb 9, 2022

How does performance compare?

@aviatesk
Copy link
Sponsor Member Author

aviatesk commented Feb 9, 2022

@nanosoldier runbenchmarks(!"scalar", vs=":master")

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

Copy link
Member

@Keno Keno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine by me. I did the same for the purity code, which needs to know the same information, so we're already relying on correctness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants