On Wed, Jul 4, 2012 at 2:04 PM, Ronald S. Bultje <[email protected]> wrote:
> Hi,
>
> On Wed, Jul 4, 2012 at 12:36 PM, Måns Rullgård <[email protected]> wrote:
>> "Ronald S. Bultje" <[email protected]> writes:
>>
>>> Hi,
>>>
>>> On Wed, Jul 4, 2012 at 10:15 AM, Måns Rullgård <[email protected]> wrote:
>>>> "Ronald S. Bultje" <[email protected]> writes:
>>>>
>>>>> From: "Ronald S. Bultje" <[email protected]>
>>>>>
>>>>> ---
>>>>>  configure            |    9 +++++++++
>>>>>  libavutil/internal.h |    6 +++++-
>>>>>  2 files changed, 14 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/configure b/configure
>>>>> index 351d8a0..4fc20a2 100755
>>>>> --- a/configure
>>>>> +++ b/configure
>>>>> @@ -1118,7 +1118,9 @@ HAVE_LIST="
>>>>>      MapViewOfFile
>>>>>      memalign
>>>>>      mkstemp
>>>>> +    mm_empty
>>>>>      mmap
>>>>> +    mmintrin_h
>>>>>      nanosleep
>>>>>      netinet_sctp_h
>>>>>      poll_h
>>>>> @@ -2646,6 +2648,13 @@ check_cc <<EOF && enable inline_asm
>>>>>  void foo(void) { __asm__ volatile ("" ::); }
>>>>>  EOF
>>>>>
>>>>> +if check_header mmintrin.h; then
>>>>> +    check_cc <<EOF && enable mm_empty
>>>>> +#include <mmintrin.h>
>>>>> +int main (void) { _mm_empty(); return 0; }
>>>>> +EOF
>>>>> +fi
>>>>
>>>> The previous patch used intrin.h, now it's mmintrin.h.  Please explain.
>>>> Looking around my hard drive, most x86 compilers seem to have a
>>>> compatible mmintrin.h, so I guess this is better.
>>>
>>> Sample code on MSDN uses intrin.h, but the docs on MSDN (and from
>>> Intel) say it's in mmintrin.h (and it indeed is). So I followed the
>>> docs, which allows it to compile with e.g. gcc also (which I think
>>> lacks intrin.h).
>>
>> Makes sense.  Do you know who, if anyone, defines what goes into that
>> header?
>
> No idea. Maybe Intel?

Also I'm waiting for your check_code so I can rebase my patch on top
of that and commit it (without have_mmintrin_h).

Ronald
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to