I noticed this message in the release notes for 0.24.4:
This release also contains some basic support for using the NEON
acceleration on iOS, although actually building pixman on that platform
remains difficult.
I was curious about what was so difficult about building pixman for iOS and
of
pixman_arm_neon.S?
Jeremy Huddleston wrote:
I noticed this message in the release notes for 0.24.4:
This release also contains some basic support for using the NEON
acceleration on iOS, although actually building pixman on that platform
remains difficult.
I was curious about what was so
I just got my tinderbox back up today and noticed this build regression in
pixman. I haven't looked into it yet, but git-log blames Matt ;)
http://tinderbox.x.org/builds/2012-02-22-0001/logs/pixman/#build
The warnings are harmless. I wish the error was more verbose, but that's all I
got.
: [14208344964f341a7b4a704b05cf4804c23792e9] mmx: Use _mm_mulhi_pu16
git bisect bad 14208344964f341a7b4a704b05cf4804c23792e9
# good: [69ed71fad11d541f89eee1238c587a03a9cf59cb] mmx: enable over_x888_8_
on ARM/iwMMXt
git bisect good 69ed71fad11d541f89eee1238c587a03a9cf59cb
On Feb 21, 2012, at 11:27 PM, Jeremy Huddleston
It doesn't look like it's an issue with clang not knowing that __N is a
compile-time constant. It does look like it's not understanding K.
With Søren's patch, I'm now getting:
fatal error: error in backend: Unsupported asm: input constraint with a
matching output constraint of
I'd rather check what it chokes on rather than just erroring out if it's
__clang__ ... that way when it is fixed, newer versions will just work
On Feb 23, 2012, at 3:45 PM, Søren Sandmann sandm...@cs.au.dk wrote:
From: Søren Sandmann Pedersen s...@redhat.com
There are several issues with
Im swamped but will do so hopefully next week unless you plan on tagging soon.
Please let me know if that isnt soon enough
the blanket no mmx on clang patch has my ack in the mean time
thanks
Sent from my iPhone...
On Feb 23, 2012, at 16:01, sandm...@cs.au.dk (Søren Sandmann) wrote:
Jeremy
This reverts commit 5eb4c12a79b3017ec6cc22ab756f53f225731533.
---
configure.ac |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/configure.ac b/configure.ac
index 17e30f5..c3c711c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -294,9 +294,6 @@
Signed-off-by: Jeremy Huddleston jerem...@apple.com
---
configure.ac |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/configure.ac b/configure.ac
index c3c711c..1ca3c02 100644
--- a/configure.ac
+++ b/configure.ac
@@ -297,6 +297,15 @@ AC_COMPILE_IFELSE
Signed-off-by: Jeremy Huddleston jerem...@apple.com
---
pixman/pixman-cpu.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/pixman/pixman-cpu.c b/pixman/pixman-cpu.c
index bb97ae3..1060f47 100644
--- a/pixman/pixman-cpu.c
+++ b/pixman/pixman-cpu.c
@@ -666,6 +666,7
This code was pretty much coppied from a similar commit that I made to
xorg-server in April.
cf: xorg/xserver: bb4d145bd25e2aee988b100ecf1105ea3b6a40b8
Signed-off-by: Jeremy Huddleston jerem...@apple.com
---
configure.ac | 26 ++
pixman/pixman-compiler.h
On Mar 8, 2012, at 09:51, Matt Turner wrote:
On Thu, Mar 8, 2012 at 5:41 PM, Jeremy Huddleston jerem...@apple.com wrote:
Signed-off-by: Jeremy Huddleston jerem...@apple.com
---
configure.ac |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/configure.ac b
On Mar 8, 2012, at 10:41, Siarhei Siamashka wrote:
On Thu, Mar 8, 2012 at 8:31 PM, Jeremy Huddleston jerem...@apple.com wrote:
On Mar 8, 2012, at 09:51, Matt Turner wrote:
Newer clangs support the K constraint? Fixed in response to its use
in pixman? :)
Unfortunately, I'm just being
Silence warnings that could make -Werror give a false negative
Use signed char to avoid cases where int8_t isn't declared
Reported-by: Mike Lothian m...@fireburn.co.uk
Signed-off-by: Jeremy Huddleston jerem...@apple.com
---
configure.ac |6 +++---
1 file changed, 3 insertions(+), 3 deletions
On Mar 14, 2012, at 16:39, Matt Turner wrote:
This causes test failures
/bin/sh: line 5: 10408 Segmentation fault ${dir}$tst
FAIL: scaling-test
/bin/sh: line 5: 10429 Floating point exception${dir}$tst
FAIL: affine-test
Test 629 failed
Operator: CONJOINT_ATOP
On Mar 8, 2012, at 10:51, Jeremy Huddleston wrote:
On Mar 8, 2012, at 10:41, Siarhei Siamashka wrote:
On Thu, Mar 8, 2012 at 8:31 PM, Jeremy Huddleston jerem...@apple.com wrote:
On Mar 8, 2012, at 09:51, Matt Turner wrote:
Newer clangs support the K constraint? Fixed in response
getisax() usage is unchanged between 0.24.4 and 0.25.2.
pixman_image_set_clip_region32 has been around since 2008.
Can you please include your full build log (for both the 0.24.4 and 0.25.2
failures).
What system are you seeing this on (OS, architecture, toolchain versions)?
On Mar 24, 2012,
:
On 2012-03-25 11:57:54 -0600 Jeremy Huddleston jerem...@freedesktop.org
wrote:
You just included the config logs. Can you please include the build logs as
well (the terminal output).
Your config.log clearly shows that you don't have getisax, so I don't see
why you would be having issues
On Mar 27, 2012, at 5:24 PM, cu cairou...@yahoo.com wrote:
Configuration script detects none, and in general does not work with iOS
(fails on all sorts of obvious things).
Like what? Did you follow my advise from an earlier email:
SDK=$(xcode-select
I'm not seeing any problem. That build log shows that it built successfully...
On Mar 29, 2012, at 10:22 PM, Germán Arias ger...@xelalug.org wrote:
On 2012-03-27 10:59:27 -0600 Jeremy Huddleston jerem...@freedesktop.org
wrote:
Please build verbosely (make V=1) and provide that log. Also
Newer clangs support the K constraint? Fixed in response to its use
in pixman? :)
And to close the loop on this, the fix has landed in clang trunk and will be
in 3.1:
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120319/055254.html
And the other half of the issue seems to
On Apr 11, 2012, at 11:33 AM, Matt Turner matts...@gmail.com wrote:
I feel like we're going in circles and I don't understand what problem
with the previously attached patch is.
I don't either, which is why I ack'd it.
___
Pixman mailing list
On May 30, 2012, at 09:28, Ryan Schmidt pixman-20...@ryandesign.com wrote:
On May 30, 2012, at 11:15, Jeremy Huddleston wrote:
My tinderbox (yuffie) is building pixman master using clang-3.0 (from
MacPorts) for x86_64:
http://tinderbox.x.org/builds/2012-05-30-0005/logs/pixman/#build
On May 30, 2012, at 10:03 AM, Siarhei Siamashka siarhei.siamas...@gmail.com
wrote:
On Wed, May 30, 2012 at 7:15 PM, Jeremy Huddleston
jerem...@freedesktop.org wrote:
My tinderbox (yuffie) is building pixman master using clang-3.0 (from
MacPorts) for x86_64:
http://tinderbox.x.org/builds
We should maybe try using -Werror=ignored-attributes in the test, or just
prefer the first one.
On Oct 25, 2012, at 14:44, Siarhei Siamashka siarhei.siamas...@gmail.com
wrote:
On Mon, 13 Feb 2012 16:16:30 -0800
Jeremy Huddleston jerem...@apple.com wrote:
From: Jeremy Huddleston jerem
On Nov 28, 2012, at 11:52 AM, Siarhei Siamashka siarhei.siamas...@gmail.com
wrote:
Now it appears that this bug also affects mingw-w64, not just clang:
https://bugs.freedesktop.org/show_bug.cgi?id=57591
I have sent a patch to change the order of checks, but another option
to evaluate
This is not a bug in clang. It isn't a case of "the asm constraints we need
are not implemented" it is a case of the code not being valid. The error
printed by clang is correct. See this post for more details:
https://code.google.com/p/nativeclient/issues/detail?id=4201#c5
Or the description
27 matches
Mail list logo
