[x265] [PATCH] Fixed size issue in xDeQuant test code

[Praveen Tiwari]

--> Does this fix the test failures with 16bpp builds?

 It does't have any issue with 16bpp builds, Mahesh tested for all possible
cases.


On Tue, Jun 25, 2013 at 10:41 PM, Steve Borho <steve at borho.org> wrote:

>
>
>
> On Tue, Jun 25, 2013 at 7:08 AM, <praveen at multicorewareinc.com> wrote:
>
>> # HG changeset patch
>> # User praveentiwari
>> # Date 1372162110 -19800
>> # Node ID 4e7a3fc1c49854ab89de035b6bc9690627463d69
>> # Parent  2d4eb5e859db3ef478ac6483128a8445c5498283
>> Fixed size issue in xDeQuant test code
>>
>
> Queued.  Does this fix the test failures with 16bpp builds?
>
>
>>
>> diff -r 2d4eb5e859db -r 4e7a3fc1c498 source/test/mbdstharness.cpp
>> --- a/source/test/mbdstharness.cpp      Tue Jun 25 17:24:38 2013 +0530
>> +++ b/source/test/mbdstharness.cpp      Tue Jun 25 17:38:30 2013 +0530
>> @@ -203,10 +203,12 @@
>>
>>          unsigned int uiLog2TrSize = (rand() % 4) + 2;
>>
>> +        int cmp_size = sizeof(int) * iWidth * iWidth;
>> +
>>          opt(8, mintbuf1 + j, mintbuf3, iWidth, iHeight, iPer, iRem,
>> useScalingList, uiLog2TrSize, mintbuf2 + j);  // g_bitDepthY  = 8,
>> g_bitDepthC = 8
>>          ref(8, mintbuf1 + j, mintbuf4, iWidth, iHeight, iPer, iRem,
>> useScalingList, uiLog2TrSize, mintbuf2 + j);
>>
>> -        if (memcmp(mintbuf3, mintbuf4, mem_cmp_size))
>> +        if (memcmp(mintbuf3, mintbuf4, cmp_size))
>>              return false;
>>
>>          j += 16;
>> _______________________________________________
>> x265-devel mailing list
>> x265-devel at videolan.org
>> http://mailman.videolan.org/listinfo/x265-devel
>>
>
>
>
> --
> Steve Borho
>
> _______________________________________________
> x265-devel mailing list
> x265-devel at videolan.org
> http://mailman.videolan.org/listinfo/x265-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20130626/509112d2/attachment.html>