Fixed the --print-supported-cpus test

Add constraints for the test that require specific backend targets
to be registered.

Remove trailing whitespace in the doc.

Differential Revision: https://reviews.llvm.org/D63105

llvm-svn: 363475
This commit is contained in:
Ziang Wan 2019-06-14 23:34:40 +00:00
parent 69394bedc5
commit 9a2e7784b1
2 changed files with 4 additions and 2 deletions

View File

@ -326,8 +326,8 @@ number of cross compilers, or may only support a native target.
.. option:: --print-supported-cpus
Print out a list of supported processors for the given target (specified
through --target=<architecture> or -arch <architecture>). If no target is
Print out a list of supported processors for the given target (specified
through --target=<architecture> or -arch <architecture>). If no target is
specified, the system default target will be used.
.. option:: -march=<cpu>

View File

@ -1,5 +1,6 @@
// Test that the --print-supported-cpus flag works
// REQUIRES: x86-registered-target
// RUN: %clang --target=x86_64-unknown-linux-gnu \
// RUN: --print-supported-cpus 2>&1 \
// RUN: | FileCheck %s --check-prefix=CHECK-X86
@ -7,6 +8,7 @@
// CHECK-X86: corei7
// CHECK-X86: Use -mcpu or -mtune to specify the target's processor.
// REQUIRES: arm-registered-target
// RUN: %clang --target=arm-unknown-linux-android \
// RUN: --print-supported-cpus 2>&1 \
// RUN: | FileCheck %s --check-prefix=CHECK-ARM