[x265] [PATCH] asm: interp_4tap_horiz_pX sse3 10-bit

Deepthi Nandakumar deepthi at multicorewareinc.com
Wed Jun 10 15:59:02 CEST 2015


Ah, I didnt notice it then - but yes, the patch you'd sent was a folded
version of pixelToShort and the 4-tap horizontal filter.

On Wed, Jun 10, 2015 at 7:15 PM, dave <dtyx265 at gmail.com> wrote:

>  Some how my patch for 10bpp interp_4tap_horiz_pX was commited as part of
> my filterPixelToShort patch so the code is in but doesn't show up in hg.
> That's probably why it failed to build for Deepthi when she applied my
> original patch.
>
>
> On 06/09/2015 10:06 AM, chen wrote:
>
>  I guess she means last string index bug, you have sent a patch to fix it.
>  At 2015-06-10 00:59:03,dave <dtyx265 at gmail.com> <dtyx265 at gmail.com>
> wrote:
>
> Can you post the errors?  I am guessing I need to rebase this on the
> latest code and resubmit.
>
>
> On 06/08/2015 11:08 PM, Deepthi Nandakumar wrote:
>
>  Hi,
>
>  This throws build errors on a x86_64 Haswell machine.
>
> On Fri, Jun 5, 2015 at 8:23 PM, chen <chenm003 at 163.com> wrote:
>
>>  other is fine, we can push it, thanks
>>  At 2015-06-05 21:45:01,dave <dtyx265 at gmail.com> wrote:
>>
>> I prefer to keep this patch as sse3/movdqu, is there anything holding
>> this back?
>>
>> On 06/02/2015 09:44 AM, chen wrote:
>>
>>  the root cause in below
>>
>>         %elif cpuflag(sse3) && notcpuflag(ssse3)
>>             %define movu lddqu
>>         %endif
>>  I often use SSSE3 to avoid this issue.
>> of course, you can choice to keep movdqu in here
>>
>> At 2015-06-03 00:28:32,dave <dtyx265 at gmail.com> <dtyx265 at gmail.com> wrote:
>> >On 06/02/2015 09:16 AM, chen wrote:
>> >> movdqu      -> movu
>> >> others fine
>> >I am not sure why but movu here fails to build.
>> >
>> >source/common/x86/ipfilter16.asm:954: error: invalid combination of
>> >opcode and operands
>> >make[2]: *** [common/CMakeFiles/common.dir/x86/ipfilter16.asm.o] Error 1
>> >make[1]: *** [common/CMakeFiles/common.dir/all] Error 2
>> >make: *** [all] Error 2
>> >_______________________________________________
>> >x265-devel mailing list
>> >x265-devel at videolan.org
>> >https://mailman.videolan.org/listinfo/x265-devel
>>
>>
>>
>> _______________________________________________
>> x265-devel mailing listx265-devel at videolan.orghttps://mailman.videolan.org/listinfo/x265-devel
>>
>>
>>
>> _______________________________________________
>> x265-devel mailing list
>> x265-devel at videolan.org
>> https://mailman.videolan.org/listinfo/x265-devel
>>
>>
>
>
> _______________________________________________
> x265-devel mailing listx265-devel at videolan.orghttps://mailman.videolan.org/listinfo/x265-devel
>
>
>
>
> _______________________________________________
> x265-devel mailing listx265-devel at videolan.orghttps://mailman.videolan.org/listinfo/x265-devel
>
>
>
> _______________________________________________
> x265-devel mailing list
> x265-devel at videolan.org
> https://mailman.videolan.org/listinfo/x265-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20150610/9a0b664d/attachment.html>


More information about the x265-devel mailing list