On Oct 18, 2016 11:08 PM, "Ronald S. Bultje" wrote:
>
> Hi Ali,
>
> On Tue, Oct 18, 2016 at 3:57 PM, Ali KIZIL wrote:
>
> > 2016-10-18 22:44 GMT+03:00 Sven C. Dack :
> >
> > > On 18/10/16 20:26, Ali KIZIL wrote:
> > >
> > >> Hi Everyone,
> > >>
> > >> Today, I was analyzing memcpy duration in FFm
Hi Ali,
On Tue, Oct 18, 2016 at 3:57 PM, Ali KIZIL wrote:
> 2016-10-18 22:44 GMT+03:00 Sven C. Dack :
>
> > On 18/10/16 20:26, Ali KIZIL wrote:
> >
> >> Hi Everyone,
> >>
> >> Today, I was analyzing memcpy duration in FFmpeg. I noticed that it is
> >> taking longer time compared to an optimized
2016-10-18 22:44 GMT+03:00 Sven C. Dack :
> On 18/10/16 20:26, Ali KIZIL wrote:
>
>> Hi Everyone,
>>
>> Today, I was analyzing memcpy duration in FFmpeg. I noticed that it is
>> taking longer time compared to an optimized SSE, SSE2, MMX, MMX2, AVX or
>> AVX2 based memcpy operation.
>>
>> I tried m
On 18/10/16 20:26, Ali KIZIL wrote:
Hi Everyone,
Today, I was analyzing memcpy duration in FFmpeg. I noticed that it is
taking longer time compared to an optimized SSE, SSE2, MMX, MMX2, AVX or
AVX2 based memcpy operation.
I tried march=corei7-avx2 compiled FFmpeg version, it does not change the
Hi Everyone,
Today, I was analyzing memcpy duration in FFmpeg. I noticed that it is
taking longer time compared to an optimized SSE, SSE2, MMX, MMX2, AVX or
AVX2 based memcpy operation.
I tried march=corei7-avx2 compiled FFmpeg version, it does not change the
duration of memcpy operation.
I also