search for: nosimd

...tmp/test.o $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto -c /tmp/test.c -o /tmp/test.o Dependencies within extensions are not checked. For example crypto requires simd, but it can be disabled in the same march option. $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto+nosimd -c /tmp/test.c -o /tmp/test.o Dependencies between an extension and the base arch are not checked either. Dot product cannot be used with v8.0-a but it is allowed. $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+dotprod -c /tmp/test.c -o /tmp/test.o GCC AArch64 =========== For GCC AArch...

...tmp/test.o $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto -c /tmp/test.c -o /tmp/test.o Dependencies within extensions are not checked. For example crypto requires simd, but it can be disabled in the same march option. $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto+nosimd -c /tmp/test.c -o /tmp/test.o It is a bit late to reply but can the options be specified independently of "-march". i.e. -march=armv8-a -mcrypto -mnosimd etc. similar to "-msse", "-mavx" on x86. This is for situations where certain packages e.g. media packages want...

...The preferred CLI for specifying FPU/NEON units will be the use of the -march option with feature modifiers (+[no]feature). The feature modifiers according to the GCC manual are: * crypto * fp * simd (implies fp) For example, "clang -march=cortex-a57+crypto" or "clang -march=generic+nosimd". Whether or not simd (neon) is enabled by default is an orthogonal issue. We plan on implementing this interface for AArch64 Clang in future, and completely dropping the current support for -mfpu. This means that -march will become the preferred way to specify the target CPU/architecture. -...

...tmp/test.o $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto -c /tmp/test.c -o /tmp/test.o Dependencies within extensions are not checked. For example crypto requires simd, but it can be disabled in the same march option. $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto+nosimd -c /tmp/test.c -o /tmp/test.o It is a bit late to reply but can the options be specified independently of "-march". i.e. -march=armv8-a -mcrypto -mnosimd etc. similar to "-msse", "-mavx" on x86. This is for situations where certain packages e.g. media packages want...

...in this current pass. Let's get the parser fixed before changing overall behaviour. > Dependencies within extensions are not checked. For example crypto requires simd, but it can be disabled in the same march option. > > $ ./clang --target=aarch64-arm-none-eabi -march=armv8-a+crypto+nosimd -c /tmp/test.c -o /tmp/test.o > > Extensions are rejected if not recognised but not checked for compatibility. Hence the Clang crypto/simd example above is allowed with GCC too. > > $ ./aarch64-elf-gcc -march=armv8-a+crypto+nosimd -c /tmp/test.c -o /tmp/test.o > (should not be allowe...