libvpx @1.7.0_0 build fails: error: assigning to '__m512i' (vector of 8 'long long' values) from incompatible type 'int'

[laughingtiger]

when upgrading ffmpeg 3.4.1_3 < 3.4.1_4 the upgrade libvpx 1.6.1_1 < 1.7.0_0 fails with Error: Failed to build libvpx: command execution failed. See attached log file.

[laughingtiger]

log

[kencu (Ken)]

looks like the version of clang included with darwin 15 is too old to understand the new avx512 instructions in libvpx.

It builds with clang-3.9 without any trouble.

[audionuma]

log for failed build of libvpx on mac OS 10.10.5

[audionuma]

Same issue here on mac OS 10.10.5. Added main.log

[ballapete (Peter "Pete" Dyballa)]

I see the same failure on El Capitan, OS X 10.11.6. Here I see one more report:

vpx_dsp/x86/sad4d_avx512.c:27:14: warning: implicit declaration of function '_mm512_set1_epi16' is invalid in C99 [-Wimplicit-function-declaration]
  sum_ref0 = _mm512_set1_epi16(0);
             ^

The code is:

   23	  ref0 = ref[0];
   24	  ref1 = ref[1];
   25	  ref2 = ref[2];
   26	  ref3 = ref[3];
   27	  sum_ref0 = _mm512_set1_epi16(0);
   28	  sum_ref1 = _mm512_set1_epi16(0);
   29	  sum_ref2 = _mm512_set1_epi16(0);
   30	  sum_ref3 = _mm512_set1_epi16(0);

Either someone mixed up brackets or this function _mm512_set1_epi16() does not exist. The latter sounds more plausible: find only finds the string _mm512_set1_epi16 *used* on these four mentioned lines. This looks like the actual cause for the failure.

[ballapete (Peter "Pete" Dyballa)]

main.log from El Capitan, OS X 10.11.6

[kencu (Ken)]

there is no failure if you build with a newer compiler Pete. It builds through perfectly fine with clang 3.9 and newer, at least on this MacBook Pro I use day to day (and on 10.6.8, at that). Assuming configure is not mistaking avx512 support on your processor, a newer clang should fix it.

Buildbots likely tell Dave where the cutoff is.

[ryandesign (Ryan Carsten Schmidt)]

Support for _mm512_set1_epi16 was ​committed to clang trunk on May 24, 2016 so we need a version of clang released after that; looks like Xcode 8 was the first release after that so we need to blacklist {clang < 800}.

[ryandesign (Ryan Carsten Schmidt)]

In 4832398cd70dcb1879ec29d677f1c753cee8e1de/macports-ports:

libvpx: Blacklist older clang that doesn't know _mm512_set1_epi16

Closes: #55800

[Ionic (Mihai Moldovan)]

... and MP-clang < 3.9.

[Ionic (Mihai Moldovan)]

Blacklist mp-clang as well, add explicit fallback to mp-clang-3.9.

[Ionic (Mihai Moldovan)]

How about something like this?

[ryandesign (Ryan Carsten Schmidt)]

Sure.

[Mihai Moldovan <ionic@…>]

In 797915c5451d6c2fd20b1a9c9629536eb45534de/macports-ports:

multimedia/libvpx: blacklist mp-clang < 3.9.

This also forces the fallback compiler to be macports-clang-3.9, which
is mandatory on older systems that have been migrated to use libc++ and
thus override their compiler list to include mp-clang-3.7 (or the like)
at the beginning.

Fixes: #55800 (again)

[Skippern (Aun Johnsen)]

I have the same issue on macOS 10.11.6

doesn't seem the blacklist/fallback works as intended, tried forced updating with no result.