ostannard added inline comments.
================
Comment at: clang/test/Driver/arm-mfpu.c:112
+// CHECK-VFP3XD-NOT: "-target-feature" "+fp64"
+// CHECK-VFP3XD-NOT: "-target-feature" "+32"
// CHECK-VFP3XD: "-target-feature" "+vfp3"
----------------
"+d32" ?
================
Comment at: llvm/lib/Target/ARM/ARMSubtarget.h:587
bool hasVFP2() const { return HasVFPv2; }
bool hasVFP3() const { return HasVFPv3; }
----------------
Are the old functions still used anywhere? If they are not used (much), I think
it would be better to just have one set of functions for the base FPU version,
and check hasFP64 and hasD32 where needed, to avoid the rick of using the wrong
version of these functions.
================
Comment at: llvm/test/MC/ARM/armv8.3a-js.s:16
// REQ-V83: error: instruction requires: armv8.3a
-// REQ-FP: error: instruction requires: FPARMv8
+// REQ-FP: error: invalid instruction
----------------
Do you know why this diagnostic got worse?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D60691/new/
https://reviews.llvm.org/D60691
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
