-
Notifications
You must be signed in to change notification settings - Fork 221
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
Post-merge review of #1419 "Universal tensor transform feature" and #1481... #1476
Comments
@aska-0096 could you follow up with Artem's comments in #1419 asap? |
Is there any specific reason for not basing this on TransposingSolver?https://github.com/ROCmSoftwarePlatform/MIOpen/blob/0c6bdeb3ff46505d65f69a8c6e72ec0eef29835a/src/include/miopen/utility/transposing_solver.hpp#L411 |
@aska-0096 could you take a look and respond to @DrizztDoUrden 's inquiries above? Thanks! |
@DrizztDoUrden Sorry for late reply. I'd like to give three main advantage in tensor reorder solver. Performance:
Completeness: |
Can we close this one since #1481 is merged? |
@junliume This can be closed after resolving all comments in |
7 comments from #1419 (review) are not resolved yet; couple of them are red. |
Description updated with #1481 (review). |
Description updated. @junliume Now this is of |
UPDATE: Leftovers:
@junliume Currently this is of
normal_urgency
The 1st version of this ticket (outdated)
All review comments must be resolved (the most important ones are marked with 🔴).
/cc @aska-0096 @shaojiewang @DrizztDoUrden
@junliume Currently this is of high_urgency
The text was updated successfully, but these errors were encountered: