Go to file
Tomoaki Teshima b2ad7cd9c0 add feature to convert FP32(float) to FP16(half)
* check compiler support
  * check HW support before executing
  * add test doing round trip conversion from / to FP32
  * treat array correctly if size is not multiple of 4
  * add declaration to prevent warning
  * make it possible to enable fp16 on 32bit ARM
  * let the conversion possible on non-supported HW, too.
  * add test using both HW and SW implementation
2016-05-21 21:31:33 +09:00
.github move GitHub templates into .github folder 2016-03-04 14:20:25 +03:00
3rdparty Updates for XCode 7.3 2016-04-17 20:21:29 +03:00
apps add a cascade classifier model visualisation tool for master branch 2016-05-11 08:56:42 +02:00
cmake add feature to convert FP32(float) to FP16(half) 2016-05-21 21:31:33 +09:00
data Fix the missing - in file. 2016-02-18 11:28:41 +01:00
doc Merge pull request #6364 from sovrasov:interactive_calibration_app 2016-04-25 12:39:56 +00:00
include include available modules only 2016-01-20 13:07:46 +03:00
modules add feature to convert FP32(float) to FP16(half) 2016-05-21 21:31:33 +09:00
platforms Added --extra_modules_path to build_sdk.py 2016-05-12 12:36:42 +03:00
samples cppcheck: fix some reports 2016-04-29 15:41:39 +02:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Improved thrust interop tutorial. 2015-09-24 09:32:38 -04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge pull request #6244 from dreifachstein:topic-cmake-install 2016-04-05 15:23:55 +00:00
CONTRIBUTING.md add link to contributing guidelines 2015-09-17 14:15:20 +02:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md Removed gittip link 2016-02-08 11:04:19 +03:00

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/Itseez/opencv/wiki/How_to_contribute

Summary of guidelines:

  • One pull request per issue;
  • Choose the right base branch;
  • Include tests and documentation;
  • Clean up "oops" commits before submitting;
  • Follow the coding style guide.