On Fri, 24 Oct 2014 12:39:18 -0200 ferse...@br.ibm.com wrote: > > In any case, perhaps the solution is to disable supernova in ppc64el > > as well instead of adding custom flags. > > Simply disabling it for ppc64el did not do the work (completely), but > you can test it if you want =)
The problem is that in ppc64el the default compile flags include -mvsx -which also implies altivec support, so just disabling supernova doesn't work, the compiler will still try to build the altivec stuff. Doing a simple : $ gcc -dM -E - < /dev/null|grep ALTIVEC #define __ALTIVEC__ 1 #define __APPLE_ALTIVEC__ 1 on a ppc64le system will show why explicitly disabling it is needed. Evenmore so, even if it worked, much of the code assumes 32-bit pointers (eg. a table lookup in server/plugins/OscUGens.cpp:1541, so the code would break on ppc64le as it's 64-bit and little-endian. A lot of stuff would have to be fixed for that. So, unless/until it's fixed and tested for ppc64le, there isn't much one can do apart from disabling altivec completely. > I think Konstantinos would be able to give you more accurate answers > to your questions regarding altivec and simd in general. He knows a > lot of that stuff. > He is cc'ed (markos). Thanks, I just like the stuff :) Regards Konstantinos
pgpDLhphuNmyR.pgp
Description: PGP signature