-
Notifications
You must be signed in to change notification settings - Fork 15.4k
[PowerPC] Optimize select_cc with VSX compare and xxsel #65295
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
Conversation
|
Can you explain the rationale of the preference of VSX compare? We only see two cases improved in the test. Are there scenarios vector compare is better? |
|
This is splitted from https://reviews.llvm.org/D75895. Since VSX instructions can use twice registers than VMX, it does no harm to codegen. |
nemanjai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, please add a description that will reflect what the eventual commit message would be.
|
In previous plan, this patch adds patterns for
|
|
Gentle ping |
1 similar comment
|
Gentle ping |
|
Please note that I have just approved to unblock the review. I have not reviewed it yet, simply approved it to remove my blocking change request so others can review it and I will try to find time to review it myself next week. |
|
Is this still relevant? |
|
@lei137 Can you please close this if it isn't relevant or rebase to make it current and ask for another review if it is relevant? |
|
Closing this PR as we are not certain if this is still relevant for us at this time. |
VSX has 'Predicate Compare Instructions' to compare float values with specific predicates and save result into VSX register. They can be used to optimize select_cc of float types. For target CPUs without support for scalar comparisons, vector version will be used.