openvino
openvino copied to clipboard
[CPU] Add test case for precision fp16
Details:
- https://github.com/openvinotoolkit/openvino/pull/16500#issuecomment-1602581987
- add test case for conv dconv fullconnect matmul mvn pad pooling subgraph softmax
Tickets:
- CVS-110112
This PR will be closed in a week because of 2 weeks of no activity.
@usstq help to continue to review thanks
@usstq continue to review, thanks
@dmitry-gorokhov Could you please help review? Thanks!
@maxnick @EgorDuplensky Guys, please review the PR
@tiger100256-hu, general comment.
You introduced fp16
precision in almost every subgraph test. But, not all of them even need to be run in fp16
as the testing code path is not even impacted by the precision. Also, in the significant part of them the real primitive precision is not checked (because it's not necessary in many cases), thus running them in fp16
with nodes that don't support this precision ends up in running fp32
code path once again "silently". So, as the first step of the fp16
tests introduction, I suggest adding the fp16
precision only to those subgraph tests that have bf16
instances. Also, for the SL tests a rule of thumb is adding fp16
where bf16
instances exist, plus the operations, which already support fp16
in the plugin. Please perform this step first so that we can proceed with the review without being distracted by fp16
test instances that need to be removed.
@maxnick thanks, I will update it, add fp16 where bf16 instances exist
@maxnick help to continue to review thanks
@iefode could you please review again?
@usstq @maxnick @iefode help to review
Hi @maxnick Could you please review again? Thanks!
@iefode , do you have any additional comments or objections?
@iefode , do you have any additional comments or objections?
@maxnick Honestly, no. Just FYI: to hardcode some specific like type, hw device and etc in shared lib is not got good practice