Re: [Pixman] Explaining bilinear in rounding.txt

On Tue, 15 Sep 2015 15:58:12 +0100 "Ben Avison" wrote: > On Mon, 14 Sep 2015 12:53:15 +0100, Pekka Paalanen > wrote: > > > On Sat, 12 Sep 2015 01:26:48 +0100 > > "Ben Avison" wrote: > > > >> -- BILINEAR filtering: > >> > >>

Re: [Pixman] [PATCH] test: Add cover-test v5

On Fri, Sep 11, 2015 at 12:06 PM, Pekka Paalanen wrote: > On Thu, 10 Sep 2015 16:11:07 +0100 > "Ben Avison" wrote: > >> On Thu, 10 Sep 2015 13:16:22 +0100, Pekka Paalanen >> wrote: >> > Changes in v5: >> > Skip if fenced memory

Re: [Pixman] [PATCH] test: Add cover-test v5

On Wed, 16 Sep 2015 12:47:34 +0300 Oded Gabbay wrote: > On Fri, Sep 11, 2015 at 12:06 PM, Pekka Paalanen wrote: > > On Thu, 10 Sep 2015 16:11:07 +0100 > > "Ben Avison" wrote: > > > >> On Thu, 10 Sep 2015 13:16:22 +0100, Pekka

[Pixman] Benchmarked: [PATCH 1/4] Change conditions for setting FAST_PATH_SAMPLES_COVER_CLIP flags

On Fri, 4 Sep 2015 03:09:20 +0100 Ben Avison wrote: > As discussed in > http://lists.freedesktop.org/archives/pixman/2015-August/003905.html > > the 8 * pixman_fixed_e adjustment which was applied to the transformed > coordinates is a legacy of rounding errors which

Re: [Pixman] Benchmarked: [PATCH 1/4] Change conditions for setting FAST_PATH_SAMPLES_COVER_CLIP flags

On Wed, 16 Sep 2015 12:25:59 +0100, Pekka Paalanen wrote: I tried both "image" and "image16" on an x86_64 (Sandybridge), and got no performance differences in the trimmed-cairo-traces set in either baseline/cleanup or cleanup/tight. I also tried with PIXMAN_DISABLE=ssse3

Re: [Pixman] [PATCH 1/4] Change conditions for setting FAST_PATH_SAMPLES_COVER_CLIP flags

On Wed, 16 Sep 2015 03:09:50 +0100, Søren Sandmann wrote: If all existing fast paths and iterators can be changed/verified to not read outside their bounds, I have no objection to changing the meaning of the existing flag (or adding a new one if that's more