Hahnfeld added inline comments.
================
Comment at: test/Misc/target-invalid-cpu-note.c:1
+// RUN: not %clang_cc1 -triple armv5--- -target-cpu not-a-cpu -fsyntax-only %s
2>&1 | FileCheck %s --check-prefix ARM
+// ARM: error: unknown target CPU 'not-a-cpu'
----------------
Is there a reason you don't use `-verify=<prefix>` in this test? That's what
I've usually seen for checking errors and notes...
================
Comment at: test/Misc/target-invalid-cpu-note.c:3
+// ARM: error: unknown target CPU 'not-a-cpu'
+// ARM: note: valid target CPU values are: arm2,
+
----------------
Is this guaranteed to be first? If not, you might want to add `{{.*}}` to
account for future updates.
(If not using `-verify` as suggested above, you could also use `ARM-SAME` on a
new-line. This should also allow arbitrary values in between.)
https://reviews.llvm.org/D42978
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
