On Sun, 02 Oct 2011 20:32 +0900, Carsten Haitzler wrote : > On Sat, 1 Oct 2011 10:12:11 -0700 Jim Kukunas > <[email protected]> > said: > > ok. big problems with sse3 on 32bit. we have to have it disabled. why? you did > it with intrinsics, and intrinsics fail without -msse3, BUT... -msse3 builds > code OPTIMIZED for sse3 - ie produces sse3 instructions even for regular c > code. this means people compile evas and then have an x86 cpu incapable of > sse3.. and presto. that binary doesnt work. that pretty much breaks backwards > compatibility for x86 - packagers will have our throats for this. > > so this is all bad. the runtime sse3 tests are pointless and moot as long as > we compile with -msse3.
Maybe you could split the code that requires -msse3 into seperate source files and compile only those with -msse3? This way you can still use intrinsics, end up with the rest of the code compiled for the correct target and get to use the SSE3 code if the runtime detection says your CPU supports it. I haven't looked at how hard it would be to acheive, but I'm not so sure rewriting GCC intrisics in plain assembly would be such a good idea. Cheers, -- Albin Tonnerre
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
