-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[CPU] [ARM] [INT8] FullyConnected #25171
[CPU] [ARM] [INT8] FullyConnected #25171
Conversation
46e41b5
to
c2d4099
Compare
b972f54
to
743281f
Compare
b56d725
to
ea6c2b2
Compare
This PR will be closed in a week because of 2 weeks of no activity. |
af1105f
to
0d7c9ec
Compare
Needed changes have been applied. |
5dc1b5c
to
80f626f
Compare
80f626f
to
44e04cf
Compare
} | ||
|
||
arm_compute::Status ACLLowpFullyConnectedExecutor::validateTensorsInfo(const ACLInfos & aclMemoryInfos) { | ||
auto &tensor_info = aclMemoryInfos[ACLArgs::ACL_SRC_0]; |
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.
Just wondering why we are setting dequantization scale on Input port? Logically I would expect it to be applied on dst port
src/plugins/intel_cpu/src/nodes/executors/acl/acl_lowp_fullyconnected.cpp
Outdated
Show resolved
Hide resolved
This reverts commit 9226262.
af0a528
to
f782508
Compare
[](const MemoryArgs& memory) -> bool { | ||
const auto dequantizationScales = getDeQuantizedScales(memory); | ||
bool isPerChannelQuantization = dequantizationScales.size() > 1; | ||
// per-channel quantization is not unsupported by ACL |
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.
minor: "not unsupported"?
### Details: - *[ARM] [INT8] FullyConnected* ### Tickets: - *CVS-149494* --------- Co-authored-by: Aleksandr Voron <[email protected]>
Details:
Tickets: