This series addresses the comments by Bill and also changes
pixman-fast-path.c so that it picks NEAREST fast paths before
BILINEAR. (I noticed this because the new filter-reduction-test.c
failed to detect a bug that I deliberately introduced).
Søren
On Fri, Mar 18, 2016 at 9:54 PM, Søren Sandmann
wrote:
> On Sun, Mar 6, 2016 at 8:06 PM, wrote:
>
>> From: Bill Spitzak
>>
>> This removes a high-frequency spike in the middle of some filters that is
>> caused by math errors all
On Sun, Mar 6, 2016 at 8:06 PM, wrote:
> From: Bill Spitzak
>
> This removes a high-frequency spike in the middle of some filters that is
> caused by math errors all being in the same direction.
>
> Signed-off-by: Bill Spitzak
> ---
>
Looks like a good idea to me. It is unfortunate that if it fails there is
not much indication which image failed but that would require a lot more
checksums.
I would guess the checksums are computed by running this with the fast
paths disabled?
___