[G-API] IE backend convert fp32 to fp16#20106
Conversation
|
@dmatveev Have a look, please |
dmatveev
left a comment
There was a problem hiding this comment.
Approved but please but the native FP16 handling in our backlog
| if (output.second->getPrecision() == IE::Precision::FP16) { | ||
| output.second->setPrecision(IE::Precision::FP32); | ||
| } | ||
| } |
There was a problem hiding this comment.
Does it simply works like this? One can set this precision and IE will be forced to provide it?
There was a problem hiding this comment.
Does it simply works like this? One can set this precision and IE will be forced to provide it?
Must work if corresponding plugin implement it, because preprocessing is done on IE core, but postprocessing like this is plugin responsibility so far.
There was a problem hiding this comment.
I believe we can provide API to configure input/output descriptor in future.
|
Maybe exposing FP16 as output type is a better & more straightforward solution |
This reverts commit 1066fcc.
|
@alalek Can it be merged ? |
[G-API] IE backend convert fp32 to fp16 * Support FP16 in IE backend
Pull Request Readiness Checklist
See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request
Patch to opencv_extra has the same branch name.