https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65837
prathamesh3492 at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from prathamesh3492 at gcc dot gnu.org --- (In reply to Ramana Radhakrishnan from comment #4) > (In reply to prathamesh3492 from comment #3) > > Hi, > > I tried to reproduce the error with a reduced test-case: > > > > #include "arm_neon.h" > > > > float32x2_t a, b, c, e; > > > > int main() > > { > > e = __builtin_neon_vmls_lanev2sf (a, b, c, 0); > > return 0; > > } > > > > arm-linux-gnueabihf-gcc -mfpu=neon test.c -flto test.c -c > > arm-linux-gnueabihf-gcc test.o -flto -o test > > lto1: fatal error: target specific builtin not available > > compilation terminated. > > Ofcourse, that's expected behaviour - you don't have support for the SIMD > intrinsics if you don't ask for it on the command line or your compiler > doesn't default to generating code for the SIMD unit. > > > lto-wrapper: fatal error: > > /home/prathamesh.kulkarni/gnu-toolchain/gcc-chromium-arm-linux-gnueabihf/ > > builds/destdir/x86_64-unknown-linux-gnu/bin/arm-linux-gnueabihf-gcc returned > > 1 exit status > > compilation terminated. > > > > However passing -mfpu=neon for linking works: > > arm-linux-gnueabihf-gcc -mfpu=neon test.o -flto -o test > > > > I suppose similar thing must be happening during linking > > libshared_memory_support.so for chromium build ? > > I couldn't see -mfpu=neon in the command line used for linking > > libshared_memory_support.so > > RESOLVED INVALID then ? Yeah, silly mistake from my side, sorry for the noise. Regards, Prathamesh > > regards > Ramana > > > > > Thank you > > Prathamesh