aboutsummaryrefslogtreecommitdiffstats
path: root/tests/dnn/dnn-layer-mathbinary-test.c
Commit message (Collapse)AuthorAgeFilesLines
* tests/dnn: Make DNN tests regular libavfilter testsAndreas Rheinhardt2021-12-191-214/+0
| | | | | | | | | | | | | | | | | They test libavfilter internal API, so they should be libavfilter test programs (which implies: linked statically to libavfilter to access internal APIs and linked normally (statically or dynamically depending upon the build configuration) against all the other libs). Right now, they are always linked statically against all libs, which is a significant size waste compared to shared libs as all of libavcodec has been pulled in despite not being really used. This also leads to linking failures on systems for which av_export_avutil is intended: libavcodec does not expect to be linked statically against the library providing avpriv_(cga|vga16)_font in this case. This is fixed by this commit. Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
* tests/dnn: fix build issue after function name changedGuo, Yejun2021-01-221-3/+3
|
* dnn/native: add log error messageTing Fu2020-08-251-3/+3
| | | | Signed-off-by: Ting Fu <ting.fu@intel.com>
* dnn_backend_native_layer_mathbinary: add floormod supportMingyu Yin2020-08-241-0/+5
| | | | Signed-off-by: Mingyu Yin <mingyu.yin@intel.com>
* dnn-layer-mathbinary-test: add unit test for minimumGuo, Yejun2020-05-081-0/+5
| | | | Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
* dnn-layer-mathbinary-test: Fix tests for cases with extra intermediate precisionMartin Storsjö2020-04-241-1/+1
| | | | | | | | | | | | | | | | | | | | | This fixes tests on 32 bit x86 mingw with clang, which uses x87 fpu by default. In this setup, while the get_expected function is declared to return float, the compiler is (especially given the optimization flags set) free to keep the intermediate values (in this case, the return value from the inlined function) in higher precision. This results in the situation where 7.28 (which actually, as a float, ends up as 7.2800002098), multiplied by 100, is 728.000000 when really forced into a 32 bit float, but 728.000021 when kept with higher intermediate precision. For the multiplication case, a more suitable epsilon would e.g. be 2*FLT_EPSILON*fabs(expected_output), but just increase the current hardcoded threshold for now. Signed-off-by: Martin Storsjö <martin@martin.st>
* dnn-layer-mathbinary-test: add unit test for divideGuo, Yejun2020-04-221-0/+5
| | | | Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
* dnn-layer-mathbinary-test: add unit test for 'mul'Guo, Yejun2020-04-221-0/+5
| | | | Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
* dnn-layer-mathbinary-test: add unit test for addGuo, Yejun2020-04-221-17/+38
| | | | Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
* dnn-layer-mathbinary-test: add unit test for subtractionGuo, Yejun2020-04-071-0/+173
Signed-off-by: Guo, Yejun <yejun.guo@intel.com>