39e3085a55
This change does two kinds of splits:
- Splits each target into a different file. Some targets are left in the
same files, such as riscv32/64 and x86/_64 as these tests and lists are
very similar.
- Splits up the very long 'note:' lines which contain a list of CPUs,
using `CHECK-SAME`. There was a note about this not being possible
before, but with `{{^}}`, this is now possible -- I have
verified that this does the right thing if a single CPU anywhere in the
list is left out.
These tests had become quite annoying to change when adding a CPU, and I
believe this change makes these easier to maintain, and should cut down
on conflicts in these files (or at least makes conflicts easier to
resolve).
I apologise in advance for downstream conflicts, but hopefully that's a
small amount of short term pain, in return for fewer conflicts in
future.
27 lines
969 B
C
27 lines
969 B
C
// This test uses '<prefix>-SAME: {{^}}' to start matching immediately where the
|
|
// previous check finished matching (specifically, caret is not treated as
|
|
// matching a start of line when used like this in FileCheck).
|
|
|
|
// RUN: not %clang_cc1 -triple mips--- -target-cpu not-a-cpu -fsyntax-only %s 2>&1 | FileCheck %s
|
|
// CHECK: error: unknown target CPU 'not-a-cpu'
|
|
// CHECK-NEXT: note: valid target CPU values are:
|
|
// CHECK-SAME: {{^}} mips1
|
|
// CHECK-SAME: {{^}}, mips2
|
|
// CHECK-SAME: {{^}}, mips3
|
|
// CHECK-SAME: {{^}}, mips4
|
|
// CHECK-SAME: {{^}}, mips5
|
|
// CHECK-SAME: {{^}}, mips32
|
|
// CHECK-SAME: {{^}}, mips32r2
|
|
// CHECK-SAME: {{^}}, mips32r3
|
|
// CHECK-SAME: {{^}}, mips32r5
|
|
// CHECK-SAME: {{^}}, mips32r6
|
|
// CHECK-SAME: {{^}}, mips64
|
|
// CHECK-SAME: {{^}}, mips64r2
|
|
// CHECK-SAME: {{^}}, mips64r3
|
|
// CHECK-SAME: {{^}}, mips64r5
|
|
// CHECK-SAME: {{^}}, mips64r6
|
|
// CHECK-SAME: {{^}}, octeon
|
|
// CHECK-SAME: {{^}}, octeon+
|
|
// CHECK-SAME: {{^}}, p5600
|
|
// CHECK-SAME: {{$}}
|