gcc; arm64; aarch64; unrecognized command line option '-mfpu=neon'

gcc arm neon arm64 linaro
user3124812 picture user3124812 · Apr 24, 2015 · Viewed 20.4k times · Source

I got compilation error:

unrecognized command line option '-mfpu=neon'*
when tried to compile with -mfpu=neon flag. Actually, any 'mfpu' options I tried failed. However in documentation this flag is mentioned, so it should be valid

What is wrong with this key? How could I tell compiler to use NEON?

Linaro GNU aarch64 linux tools 4.8 are used.

Thanks.

Answer

Charles Baylis picture Charles Baylis · Apr 27, 2015

Advanced SIMD (aka NEON) is mandatory for AArch64, so no command line option is needed to instruct the compiler to use NEON.

If you want to enable auto vectorization optimisations so that the compiler automatically uses NEON instructions, then compile with -O3 or -O2 -ftree-vectorize.

The AArch64 and ARM backends are completely separate in gcc. The ARM back end only targets the traditional 32 bit ARM instructions sets (ARM, Thumb, Thumb-2). This is in contrast to the situation with x86, where the 32 bit and 64 bit code generation is combined into a single GCC back end.

Related questions

gcc-arm-linux-gnueabi command not found

I am trying to install the gnu arm toolchain for ubuntu. I first downloaded the tar from CodeSourcery. However when I go into the bin folder, I cannot run any of the binaries. I have tried with ./ and without and …

Read More
ARM compilation error, VFP registers used by executable, not object file

I have been having this problem for the last few days and I can't get my head around what is really happening here, or what is the problem. I have a makefile with these flags: CC = arm-linux-gnueabihf-gcc-4.6 FLAGS = -O3 -march=…

Read More
Differences between arm64 and aarch64

I have two "unlocked" devices, an iPad mini 3, and a Galaxy Edge 6, both endowed with a terminal and a minimalistic set of unix commands. I thought both devices have arm64 processors but when I ran uname -a on both devices …

Read More