diff options
| author | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | 2019-07-14 18:32:42 +0000 |
|---|---|---|
| committer | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | 2019-07-14 18:32:42 +0000 |
| commit | 24cacf9c56f0b55534e98941cc8675a9a7489c37 (patch) | |
| tree | 8f1feaa6b438ca77f30acf6b91697b63b566f776 /llvm/lib/Transforms | |
| parent | aae0cb67ed79bb7dddcda3438afd1263104cc689 (diff) | |
| download | bcm5719-llvm-24cacf9c56f0b55534e98941cc8675a9a7489c37.tar.gz bcm5719-llvm-24cacf9c56f0b55534e98941cc8675a9a7489c37.zip | |
[clang][Driver][ARM] Favor -mfpu over default CPU features
When processing the command line options march, mcpu and mfpu, we store
the implied target features on a vector. The change D62998 introduced a
temporary vector, where the processed features get accumulated. When
calling DecodeARMFeaturesFromCPU, which sets the default features for
the specified CPU, we certainly don't want to override the features
that have been explicitly specified on the command line. Therefore, the
default features should appear first in the final vector. This problem
became evident once I added the missing (unhandled) target features in
ARM::getExtensionFeatures.
Differential Revision: https://reviews.llvm.org/D63936
llvm-svn: 366027
Diffstat (limited to 'llvm/lib/Transforms')
0 files changed, 0 insertions, 0 deletions
