fpetrogalli added inline comments.
Herald added a subscriber: danielkiss.

================
Comment at: test/Driver/aarch64-cpus.c:518
+// RUN: %clang -target aarch64 -march=armv8.4-a -### -c %s 2>&1 | FileCheck 
-check-prefix=GENERICV84A-NO-FP16FML %s
+// GENERICV84A-NO-FP16FML-NOT: "-target-feature" "{{[+-]}}fp16fml"
+// GENERICV84A-NO-FP16FML-NOT: "-target-feature" "{{[+-]}}fullfp16"
----------------
Hi @SjoerdMeijer , I have noticed that this test does something different from 
what gcc does (well, claims to do, I haven't checked the actual behavior on 
gcc).

From the table in [1], it seems that `armv8.4-a` implies `fp16fml`... who got 
it right? GCC or clang? Or am I missing something?

Francesco


[1] https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html#AArch64-Options 
(see the description of `-march=name`)


Repository:
  rC Clang

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D50229/new/

https://reviews.llvm.org/D50229



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
  • [PATCH] D50229: [ARM]... Francesco Petrogalli via Phabricator via cfe-commits

Reply via email to