search for: mcrypto

...s intrinsics and is additive but assumes that you're not relying on codegen to emit instructions. I don't think it helps the bug linked from the GN source either. (https://crbug.com/934016) So what you have is the best we can do right now. Looking forward the problem I have with a '-mcrypto' is two fold: * What about other optional extensions? We'd need to add one for each, or at least every one people ask for and ideally get that into GCC too. * crypto specifically can mean different things depending on the base architecture. From Clang's point of view that's fine a...

...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 to enable certain features based on runtime cpu detection. To enable e.g. "crypto", they are also forced to choose a march, but that could override...

Hi, Below is a document detailing changes we'd like to make to Clang/LLVM to improve the usability of the target options for ARM and AArch64. To keep things simple the proposed changes are listed at the start and you can find the supporting examples at the end of the document. I look forward to your feedback. Thanks, David Spickett. RFC New Clang target feature selection options for