[Pixman] [PATCH 01/14] pixman-fast-path.c: Pick NEAREST affine fast paths before BILINEAR ones

[Bill Spitzak]

I can confirm this fixes the problem and allows multiple fast path flags 
to be set.

Reviewed-by: Bill Spitzak <spitzak at gmail.com>

On 04/11/2016 07:36 PM, Søren Sandmann Pedersen wrote:
> When a BILINEAR filter is reduced to NEAREST, it is possible for both
> types of fast paths to run; in this case, the NEAREST ones should be
> preferred as that is the simpler filter.
>
> Signed-off-by: Soren Sandmann <soren.sandmann at gmail.com>
> ---
>   pixman/pixman-fast-path.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/pixman/pixman-fast-path.c b/pixman/pixman-fast-path.c
> index 53d4a1f..b4daa26 100644
> --- a/pixman/pixman-fast-path.c
> +++ b/pixman/pixman-fast-path.c
> @@ -3258,9 +3258,9 @@ static const pixman_iter_info_t fast_iters[] =
>       },
>
>   #define AFFINE_FAST_PATHS(name, format, repeat)				\
> -    SEPARABLE_CONVOLUTION_AFFINE_FAST_PATH(name, format, repeat)	\
> +    NEAREST_AFFINE_FAST_PATH(name, format, repeat)			\
>       BILINEAR_AFFINE_FAST_PATH(name, format, repeat)			\
> -    NEAREST_AFFINE_FAST_PATH(name, format, repeat)
> +    SEPARABLE_CONVOLUTION_AFFINE_FAST_PATH(name, format, repeat)
>
>       AFFINE_FAST_PATHS (pad_a8r8g8b8, a8r8g8b8, PAD)
>       AFFINE_FAST_PATHS (none_a8r8g8b8, a8r8g8b8, NONE)
>