-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[PIR] 解决废弃算子mul op 在新 IR 下的translator问题 #56550
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
@DrRyanHuang 可以尝试修改
这里写的可以参考下。我们对mul的处理比较特殊,如果这样后续有问题的话,可以再@下我。 |
Sorry to inform you that ebce876's CIs have passed for more than 7 days. To prevent PR conflicts, you need to re-run all CIs manually. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry to inform you that 51b9e8c's CIs have passed for more than 7 days. To prevent PR conflicts, you need to re-run all CIs manually. |
Sorry to inform you that 62b9089's CIs have passed for more than 7 days. To prevent PR conflicts, you need to re-run all CIs manually. |
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
comment 里的建议下个PR 统一fix下~~
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.
LGTM overall. But there're two problems that we should consider.
- insert two much reshape, every pair of mul/mul_grad will lead to 6-10 additional reshape op insertions, is there some way to decrease this number?
- too much redundant code. Try to compress by some kind of abstraction like function.
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.
LGTM for op_compat
PR types
Others
PR changes
Others
Description
Others