Re: [meta-oe][PATCH] opencv: disable broken Intel FP16 detection

[Randy MacLeod <randy.macleod@windriver.com>]

On 2017-04-26 09:33 PM, Randy MacLeod wrote:
> 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 worked 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 involved many files and
> a cherry-picking explosion so it's not worthwhile.
>
> Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> ---

I'm not particularly happy with this patch but it does fix
a build problem and doesn't appear to break any arches.
It's probably best if I soak it on our build cluster and
that I take a more time to confirm that I haven't broken anything.

I'm off work until Monday now so I thought that some people on the list
might be interested in the patch or in pitching in. If not, I'll
follow up next week.

Btw, I'm pinging the opencv devs to see when the next release is
expected.

-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5