Re: [Pixman] mips* asm exports symbols that should not export

On Thu, Dec 19, 2013 at 5:20 PM, Nemanja Lukic nemanja.lu...@rt-rk.com wrote: Hi YunQiang Su, Yes, you are right, these symbols shouldn't be exported. This is due to the fact that some optimizations were compiled (not executed) With this patch, if I use mips32r2 option to build for o32, will

Re: [Pixman] mips* asm exports symbols that should not export

Hi YunQiang Su, Yes, you are right, these symbols shouldn't be exported. This is due to the fact that some optimizations were compiled (not executed) where they shouldn't. Please find attached fix, that solves this issue. In the mean time I'll submit this patch on main pixman repository. Thanks

Re: [Pixman] mips* asm exports symbols that should not export

Hi YunQiang Su, Attached is solution for unwanted symbol visibility. I'll upstream both patches soon. Thanks, Nemanja Lukic -Original Message- From: Nemanja Lukic [mailto:nemanja.lu...@rt-rk.com] Sent: Thursday, December 19, 2013 12:30 PM To: 'Yunqiang Su' Cc:

[Pixman] Use of uninitialized values (?)

Hi I just analyzed some application using valgrind. I am getting warnings like this: ==6514== Conditional jump or move depends on uninitialised value(s) ==6514==at 0x3C8DA72B04: sse2_combine_over_u (pixman-sse2.c:646) ==6514==by 0x3C8DA57CE3: general_composite_rect (pixman-general.c:199)

Re: [Pixman] Use of uninitialized values (?)

On Thu, 19 Dec 2013 22:01:46 +0100 Christian Stadelmann chris.pri...@genodeftest.de wrote: Hi I just analyzed some application using valgrind. I am getting warnings like this: ==6514== Conditional jump or move depends on uninitialised value(s) ==6514==at 0x3C8DA72B04: