On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas <james.t.kuku...@linux.intel.com> said:
> On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: > > On 14/10/11 19:20, Jim Kukunas wrote: > > > What is your compiler version and CFLAGS? > > > > > > The parameters to _mm_set_epi32 look reasonable. The only reason I could > > > imagine this failing is if your compiler isn't aligning things properly. > > > > It's the sse3 issue all over again. As you can see, his CPU doesn't > > support sse3 but sse3 code is called. > > His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
