On Tue, 6 Nov 2012 01:06:58 -0200 Lucas De Marchi <[email protected]> wrote:
> On Mon, Nov 5, 2012 at 11:07 PM, Jim Kukunas > <[email protected]> wrote: > > On Tue, Nov 06, 2012 at 01:41:01AM +0100, Vincent Torri wrote: > >> On Tue, Nov 6, 2012 at 1:32 AM, Paulo Alcantara > >> <[email protected]> wrote: > >> > On Mon, Nov 5, 2012 at 7:12 PM, Sebastian Dransfeld > >> > <[email protected]> wrote: > >> >> Program received signal SIGILL, Illegal instruction. > >> >> 0x00491f8b in _mm_lddqu_si128 (__P=0xbfffb5b0) at > >> >> /usr/lib/gcc/i686-linux-gnu/4.6/include/pmmintrin.h:111 > >> >> 111 return (__m128i) __builtin_ia32_lddqu ((char const > >> >> *)__P); (gdb) bt > >> >> #0 0x00491f8b in _mm_lddqu_si128 (__P=0xbfffb5b0) at > >> >> /usr/lib/gcc/i686-linux-gnu/4.6/include/pmmintrin.h:111 > >> >> #1 _op_blend_pas_dp_sse3 (s=0xbfffb5b0, m=0x0, c=0, > >> >> d=0xbfffb6b0, l=64) at > >> >> lib/evas/common/evas_op_blend/op_blend_pixel_sse3.c:59 #2 > >> >> 0x004b0d34 in evas_common_op_sse3_test () at > >> >> lib/evas/common/evas_op_blend/op_blend_master_sse3.c:73 #3 > >> >> 0x00465867 in evas_common_cpu_sse3_test () at > >> >> lib/evas/common/evas_cpu.c:72 #4 0x00465983 in > >> >> evas_common_cpu_feature_test (feature=0x465850 > >> >> <evas_common_cpu_sse3_test>) at lib/evas/common/evas_cpu.c:138 > >> >> #5 0x00465ad3 in evas_common_cpu_init () at > >> >> lib/evas/common/evas_cpu.c:183 > >> >> > >> >> pentium-m > >> >> flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr > >> >> pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up > >> >> bts est tm2 > >> >> > >> > > >> > Weird. Looks like SSE3 support isn't being checked properly > >> > through CPUID. > >> > >> the check in configure is not sufficient : host detection + > >> detection of a file, which exists on this pentium M. So something > >> more should be done, I guess, don't know what, though > > > > The host detection + header check is _NOT_ a check as to whether the > > processor supports SSE3, but rather whether the build environment > > can compile code with SSE3 intrinsics. > > It could be done at configure time by using AC_RUN_IFELSE to add a > check to compile and run the check. The problem is with > cross-compiling, but it would be the same for checking cpuid. I don't > think anyone is cross-compiling for a CPU supporting sse3, so it may > be safe to just disable it in this case. > > > > The real check occurs at runtime in evas_common_cpu_feature_test(), > > where we attempt to run a function consisting of the feature in > > question while trapping for SIGILL and SIGSEGV. If we catch either > > signal, we disable support for the associated feature. > > why not at configure time instead of installing the signal handlers? I'd prefer a run time check. Makes it easy when you can deliver a single package that just works, instead of SSE and non SSE versions, then leave it up to users that have no idea what the hell SSE is to pick the right one, or put up with some of them complaining about crashes. Been there, done that, just detecting at run time and doing the right thing is waaay preferable. Same goes for other CPUs that have support for optional features like SSE. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
