Lines Matching full:neon
1 Android NDK & ARM NEON instruction set extension support
22 "NEON". It provides:
31 Not all ARMv7-based Android devices will support NEON, but those that
35 files with support for NEON. What this means is that a specific compiler
36 flag will be used to enable the use of GCC ARM Neon intrinsics and
39 > http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html
46 will build all its source files with NEON support. This can be useful if
48 NEON code paths.
51 Using the .neon suffix:
55 the option of using the .neon suffix to indicate that you want to
56 corresponding source(s) to be built with Neon support. For example:
58 LOCAL_SRC_FILES := foo.c.neon bar.c
60 Will only build 'foo.c' with NEON support.
62 Note that the .neon suffix can be used with the .arm suffix too (used to
63 specify the 32-bit ARM instruction set for non-NEON instructions), but must
66 In other words, 'foo.c.arm.neon' works, but 'foo.c.neon.arm' does NOT.
72 Neon support only works when targeting the 'armeabi-v7a' or 'x86' ABI, otherwise
73 the NDK build scripts will complain and abort. Neon is partially supported on
77 # define a static library containing our NEON code
80 LOCAL_MODULE := mylib-neon
81 LOCAL_SRC_FILES := mylib-neon.c
90 As said previously, NOT ALL ARMv7-BASED ANDROID DEVICES WILL SUPPORT NEON !
91 It is thus crucial to perform runtime detection to know if the NEON-capable
109 // use NEON-optimized routines
114 // use non-NEON fallback routines instead
123 Look at the source code for the "hello-neon" sample in this NDK for an example
124 on how to use the 'cpufeatures' library and Neon intrinsics at the same time.
127 a NEON-optimized one for devices that support it.
