peter.smith added a comment. I'm not in favour of adding AArch64 support to -mcrypto -mnocrypto for a few reasons:
- Arm are trying to keep the options for controlling target features as consistent as possible with GCC and this option isn't supported in GCC (https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html) - There is http://lists.llvm.org/pipermail/llvm-dev/2018-September/126346.html which is Arm's proposal for how target options can be better supported in Clang. I think that supporting -mcrypto as well would add more complexity as there are interactions between the options. - Arm 32-bit also supports crypto so this would need to be added to Arm as well for consistency. Can you expand on why you need -m[no]crypto? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D60472/new/ https://reviews.llvm.org/D60472 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
