Files
meta-openembedded/meta-oe
Randy MacLeod 5e82995148 opencv: disable broken Intel FP16 detection
With opencv-3.2, the configuration detects if the target supports
half-precision floating-point format. This fails to compile for some
Intel targets such as skylake with an error such as:
   error: '_mm_cvtph_ps' was not declared in this scope

The configuration used to work in opencv-3.1 so revert two commits to
drop the FP16 detection even though it may make opencv slower.
The only change in the configure log is:
   - FP16: Compiler support is available
   + FP16: Compiler support is not available

The patch should be dropped when a newer version of opencv that includes commit:
   https://github.com/opencv/opencv/commit/e5d9b608c47d54e43496041595025fa282fa9de5
is available. Backporting that fix was complicated.

Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-05-09 16:00:31 +02:00
..
2016-05-10 20:18:57 +02:00
2017-04-26 20:13:31 +02:00
2017-04-18 14:21:41 +02:00
2011-07-26 21:51:39 +02:00

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: pyro
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][pyro]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][pyro][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

pyro Branch Maintainer:
Armin Kuster <akuster808@gmail.com>