Re: [Pixman] [PATCH] Add CMake build rules

Op 22-05-16 om 11:47 schreef whitequark: > On 2016-05-22 09:20, Pekka Paalanen wrote: >> [snip] >> >> For what benefit? So that people who set up cross-build toolchains and >> projects as their job have one less component to make that setup for? > > So that people would avoid the setup of

[Pixman] NEON build problems with master (0.23.7)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, When building master I get: arm-angstrom-linux-gnueabi-libtool: compile: ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize - -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 - -mthumb-interwork -mno-thumb

Re: [Pixman] An iwmmxt optimised shadowUpdateRotate16_270YX, with problems.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 26-08-11 20:54, Marko Katić schreef: Please understand that I could barely write my own name in C (or any other language) less than a year ago. Pixman sources look very scary to me and i dont think i'm up to the task of reimplementing or

Re: [Pixman] [cairo] Floating point API in Pixman

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12-08-10 12:24, Soeren Sandmann wrote: Andrea Canciani ranm...@gmail.com writes: If we can't assume that we have a (fast) FPU, There is a fairly common misconception that ARM CPUs never have hardware floating point; that may be part of why

Re: [Pixman] 0.18.0 schedule

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02-03-10 12:47, Soeren Sandmann wrote: Hi, 0.18.0 needs to be released some time this month, which is not that much time. These are things I'd definitely like to get in: * The three latest NEON fast paths