Krzysztof Kosiński writes:
> So what is the bottom line? Should we have two versions of all code,
> one using float and one using pixman_fixed_t, or is replacing
> pixman_fixed_t with float sufficient?
As far as I am concerned, using floating point is fine. I have not
heard otherwise from anybod
Krzysztof Kosiński wrote:
2010/8/16 Bill Spitzak :
The problem I am having is that this does not match how filtering of
transforms is done in any image processing software I am familiar with.
This is how all software I am familiar with works, this replaces the three
steps you show above:
2010/8/16 Bill Spitzak :
> The problem I am having is that this does not match how filtering of
> transforms is done in any image processing software I am familiar with.
>
> This is how all software I am familiar with works, this replaces the three
> steps you show above:
>
> - Figure out th
On Monday 16 August 2010 11:24:44 Xu, Samuel wrote:
> Thanks for kindly comments! It is very nice that bug#20709 also
emphasize
> similar performance issue.
Well, having bugs unresolved for such a long time is not so nice. Also see some
more comments below.
> So, let's discuss how to make
Soeren Sandmann wrote:
- interpolate to define the image on a continuous domain
- transform
- resample
The problem I am having is that this does not match how filtering of
transforms is done in any image processing software I am familiar with.
This is how all softw
So what is the bottom line? Should we have two versions of all code,
one using float and one using pixman_fixed_t, or is replacing
pixman_fixed_t with float sufficient?
How much slower is softfloat - a factor of 5, 15 or 500?
Another thing we have to take into account is that new versions of
Cair
On Thu, 2010-08-12 at 17:12 +0200, Jean-Claude Repetto wrote:
> Only high-end ARM processors of the most recent family (ARM-11) have a
> FPU.
Even that is not an accurate statement:
FPU co-processor cores are available all the way back to at least ARMv3
(ARM6 family) which is virtually prehistori
From: Søren Sandmann Pedersen
It doesn't make sense in other cases, and the computation would make
use of image->bits.{width,height} which lead to uninitialized memory
accesses when the image wasn't of type BITS.
---
pixman/pixman.c | 17 ++---
1 files changed, 10 insertions(+), 7
A new pixman release 0.18.4 is now available. This is a stable release
which contains bug fixes since 0.18.2.
NOTE: There is a known memory leak in this release when pixman is used
in multi-threaded programs on Windows. This bug is present in 0.18.0
and 0.18.2 as well. If you know how to fix it, p
Hi, Siamashka:
Thanks for kindly comments! It is very nice that bug#20709 also
emphasize similar performance issue.
So, let's discuss how to make this patch better. Here is some answers
from me, and Ma Ling will update comments on 32/64 bit question and assemble
details :
1) For
10 matches
Mail list logo
