Skip to content

Fix a PerformanceInliner crash caused by a null callee signature. #23473

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

Merged
merged 1 commit into from
Mar 22, 2019
Merged

Fix a PerformanceInliner crash caused by a null callee signature. #23473

merged 1 commit into from
Mar 22, 2019

Conversation

atrick
Copy link
Contributor

@atrick atrick commented Mar 21, 2019

This is an obvious drive-by fix. It will crash when building
Foundation after I commit changes to the pipeline. My attempts at
creating a unit test were unsuccessful because it depends on some
interaction between inlining and specialization heuristics.

This is an obvious drive-by fix. It will crash when building
Foundation after I commit changes to the pipeline. My attempts at
creating a unit test were unsuccessful because it depends on some
interaction between inlining and specialization heuristics.
@atrick
Copy link
Contributor Author

atrick commented Mar 21, 2019

@swift-ci test.

@slavapestov
Copy link
Contributor

You’ll be thrilled to know that hasAnySubstitutableParams() is going away once I figure out how to tweak the optimizer to fix the performance regression: #23291

@atrick
Copy link
Contributor Author

atrick commented Mar 21, 2019

@slavapestov Maybe #23291 will be fixed by #22445.

@atrick atrick merged commit 7e3f8d9 into swiftlang:master Mar 22, 2019
@atrick atrick deleted the fix-inline-canspecialize branch May 8, 2019 21:38
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.

2 participants