-
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
[oneDNN][INT8][FP32] INT8/FP32 elementwise_mul and INT8 elementwise_add #24812
Conversation
Allow mkldnn_reuse to create primitive descriptors with attributes
test=develop
test=develop
test=develop
Thanks for your contribution! |
No idea what happened, didn't touch anything there.
Again, no idea what went wrong there, didn't touch the file. @luotao1 do you know if there are any ongoing fixes for PR-CI-Coverage and PR_Windows_CI (Paddle Windows)? @jczaja @wojtuss you can start the review, as no tests currently fail, CIs only fail because of missing approvals, or random PR-unrelated compilation failures. |
fixed by #24800, just rerun it, and I have already rerun Windows.
It seems not the addition of int8 attributes, I have rerun it at first. |
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
test=develop
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
Could you split this PR into several ones? The reason is:
|
Following files are strictly connected to one another and concern addition of elementwise_kernels:
This is a bugfix required for int8 tests to pass
This is a bugfix required for int8 inplace tests to pass
Do you want me to split this into 3 such PRs? |
It's better to split this into 3 such PRs. Besides, how about remove |
|
The fail reason for
Yes, it's better to move it to separate PR, which is easy for QA review. And your current PR is much more clearer.
I see the other two PRs, which are quick to be merged. But if they are in one PR, the approval may take some time. |
Alright, I moved it to #24855
That's assuming no random CI failures 😉 |
Work on this functionality is continued in PR #24984. Closing |
PR types: New features
PR changes: OPs
Describe:
PRs to be merged before this one:
#24853
#24854
#24855