Skip to content

Fix a warning in LICM in release builds #18998

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
Aug 28, 2018

Conversation

shajrawi
Copy link

rdar://problem/43623829

@shajrawi
Copy link
Author

@swift-ci Please smoke test and merge

shajrawi referenced this pull request Aug 27, 2018
…eed to be executed

In some instances, some instructions, like ref_element_addr, can be hoisted outside of loops even if they are not guaranteed to be executed.

We currently don’t support that / bail. We only try to do so / do further analysis only for begin_access because they are extremely heavy.

However, we need to support hosting of ref_element_addr in that case, if it does not have a loop dependent operand, in order to be able to hoist begin_access instructions in some benchmarks.

Initial local testing shows that this PR, when we enable exclusivity, improves the performance of a certain internal benchmark by over 40%

See rdar://problem/43623829
@shajrawi
Copy link
Author

@swift-ci Please smoke test and merge

@shajrawi
Copy link
Author

@swift-ci Please smoke test OS X

@shahmishal
Copy link
Member

@swift-ci Please smoke test Linux

@shajrawi shajrawi merged commit d1340c8 into swiftlang:master Aug 28, 2018
@shajrawi shajrawi deleted the fix_licm_warning branch August 28, 2018 17:11
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