On Thu, May 8, 2014 at 5:16 PM, Gustavo Sverzut Barbieri <[email protected]> wrote: > change it to --disable-optimizations or --disable-simd? Possible > --without-optimizations={neon|sse|...} but i don't see a reason why one > would disable mmx and not sse and vice versa. > > the reason I ask such is to avoid growing the number of options too much
I was wondering if that would ever happen. The problem show up with ARMv6 as GCC would not be able to produce a binary for our code, but pass the check in configure.ac. I am wondering if that would ever happen with x86. If yes, then that should be fix. > On Thu, May 8, 2014 at 11:25 AM, Cedric BAIL <[email protected]> wrote: > >> cedric pushed a commit to branch master. >> >> >> http://git.enlightenment.org/core/efl.git/commit/?id=79c4baf1ccaedf33a2b187475850572f28ff7e4a >> >> commit 79c4baf1ccaedf33a2b187475850572f28ff7e4a >> Author: Cedric Bail <[email protected]> >> Date: Thu May 8 16:24:04 2014 +0200 >> >> autotools: make it possible to forcibly disable neon. >> --- >> configure.ac | 47 ++++++++++++++++++++++++++++++----------------- >> 1 file changed, 30 insertions(+), 17 deletions(-) >> >> diff --git a/configure.ac b/configure.ac >> index 061b5ca..e437be8 100644 >> --- a/configure.ac >> +++ b/configure.ac >> @@ -477,6 +477,17 @@ build_cpu_sse3="no" >> build_cpu_altivec="no" >> build_cpu_neon="no" >> >> +want_neon="yes" >> +AC_ARG_ENABLE([neon], >> + [AC_HELP_STRING([--disable-neon], [disable neon support >> @<:@default=enable@:>@])], >> + [ >> + if test "x${enableval}" = "xyes"; then >> + want_neon="yes" >> + else >> + want_neon="no" >> + fi >> + ]) >> + >> SSE3_CFLAGS="" >> ALTIVEC_CFLAGS="" >> NEON_CFLAGS="" >> @@ -541,23 +552,25 @@ case $host_cpu in >> fi >> ;; >> arm*) >> - build_cpu_neon="yes" >> - AC_MSG_CHECKING([whether to use NEON instructions]) >> - CFLAGS_save="${CFLAGS}" >> - CFLAGS="${CFLAGS} -mfpu=neon" >> - AC_TRY_COMPILE([#include <arm_neon.h>], >> - [asm volatile ("vqadd.u8 d0, d1, d0\n")], >> - [ >> - AC_MSG_RESULT([yes]) >> - AC_DEFINE([BUILD_NEON], [1], [Build NEON Code]) >> - build_cpu_neon="yes" >> - NEON_CFLAGS="-mfpu=neon" >> - ], >> - [ >> - AC_MSG_RESULT([no]) >> - build_cpu_neon="no" >> - ]) >> - CFLAGS="${CFLAGS_save}" >> + if test "x${want_neon}" = "xyes"; then >> + build_cpu_neon="yes" >> + AC_MSG_CHECKING([whether to use NEON instructions]) >> + CFLAGS_save="${CFLAGS}" >> + CFLAGS="${CFLAGS} -mfpu=neon" >> + AC_TRY_COMPILE([#include <arm_neon.h>], >> + [asm volatile ("vqadd.u8 d0, d1, d0\n")], >> + [ >> + AC_MSG_RESULT([yes]) >> + AC_DEFINE([BUILD_NEON], [1], [Build NEON Code]) >> + build_cpu_neon="yes" >> + NEON_CFLAGS="-mfpu=neon" >> + ], >> + [ >> + AC_MSG_RESULT([no]) >> + build_cpu_neon="no" >> + ]) >> + CFLAGS="${CFLAGS_save}" >> + fi >> ;; >> esac >> >> >> -- >> >> >> > > > -- > Gustavo Sverzut Barbieri > -------------------------------------- > Mobile: +55 (19) 99225-2202 > Contact: http://www.gustavobarbieri.com.br/contact > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Cedric BAIL ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
