On Mon, Jun 12, 2017 at 4:18 PM, Diego Biurrun <di...@biurrun.de> wrote:
> On Mon, Jun 12, 2017 at 04:15:27PM -0400, Sean McGovern wrote:
>> On Jun 12, 2017 3:53 PM, "Diego Biurrun" <di...@biurrun.de> wrote:
>> --- a/configure
>> +++ b/configure
>> @@ -4458,29 +4458,19 @@ elif enabled ppc; then
>> # check if our compiler supports Motorola AltiVec C API
>> - check_cc <<EOF || disable altivec
>> -#include <altivec.h>
>> -int main(void) {
>> - vector signed int v1 = (vector signed int) { 0 };
>> - vector signed int v2 = (vector signed int) { 1 };
>> - v1 = vec_add(v1, v2);
>> - return 0;
>> -}
>> -EOF
>> + check_code cc altivec.h "vector signed int v1 = (vector signed
>> int) { 0 };
>> + vector signed int v2 = (vector signed
>> int) { 1 };
>> + v1 = vec_add(v1, v2);" ||
>> + disable altivec
>>
>> enabled altivec || warn "Altivec disabled, possibly missing --cpu
>> flag"
>> fi
>>
>> Traditionally, modifying tests like this have been brittle for us -- has it
>> had a spin on ORACLE? If not would you mind doing so?
>
> I tested this on the same box that does the ppc (cross)builds for oracle,
> so I'd say yes.
>
I checked it on POWER7 and POWER8, it seems OK.
-- Sean McG.
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
