llvm-project/clang/test/CodeGen/arm-build-attributes.c

// RUN: %clang --target=arm-none-eabi -x c - -o - -S < %s -mcpu=cortex-a5 -mfpu=vfpv4-d16 | FileCheck %s
// REQUIRES: arm-registered-target
// CHECK: .fpu vfpv4-d16
void foo() {}
[TargetInfo] Sort target features before passing them to the backend Passing the features in random order will lead to unpredictable results when some of the features are related (like the architecture-version features on ARM). It might be possible to fix this particular case in the ARM target code, to avoid adding overlapping target features. But we should probably be sorting in any case: the behavior shouldn't depend on StringMap's hashing algorithm. Differential Revision: https://reviews.llvm.org/D46030 llvm-svn: 330861 2018-04-26 03:14:05 +08:00			`// RUN: %clang --target=arm-none-eabi -x c - -o - -S < %s -mcpu=cortex-a5 -mfpu=vfpv4-d16 \| FileCheck %s`
			`// REQUIRES: arm-registered-target`
			`// CHECK: .fpu vfpv4-d16`
			`void foo() {}`