diff options
author | Diana Picus <diana.picus@linaro.org> | 2016-07-07 09:11:39 +0000 |
---|---|---|
committer | Diana Picus <diana.picus@linaro.org> | 2016-07-07 09:11:39 +0000 |
commit | 575f2bb28737bc5bfbe625b470a23be68466bffa (patch) | |
tree | db8b334abd918629f9f1190b06701cbcdfd5925f /lldb/packages/Python/lldbsuite/test/expression_command/macros/TestMacros.py | |
parent | ad00756301c73771a058f23c77226627c8e27f9a (diff) | |
download | bcm5719-llvm-575f2bb28737bc5bfbe625b470a23be68466bffa.tar.gz bcm5719-llvm-575f2bb28737bc5bfbe625b470a23be68466bffa.zip |
[ARM] Do not test for CPUs, use SubtargetFeatures. Also remove 1 flag
This is a follow-up for r273544.
The end goal is to get rid of the isSwift / isCortexXY / isWhatever methods.
This commit also removes a command line flag that isn't used in any of the tests:
check-vmlx-hazards. It can be replaced easily with the mattr mechanism, since
this is now a subtarget feature.
There is still some work left regarding FeatureExpandMLx. In the past MLx
expansion was enabled for subtargets with hasVFP2(), until r129775 [1] switched
from that to isCortexA9, without too much justification.
In spite of that, the code performing MLx expansion still contains calls to
isSwift/isLikeA9, although the results of those are pretty clear given that
we're only enabling it for the A9.
We should try to enable it for all targets that have FeatureHasVMLxHazards, as
it seems to be closely related to that behaviour, and if that is possible try to
clean up the MLx expansion pass from all calls to isWhatever. This will require
some performance testing, so it will be done in another patch.
[1] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20110418/119725.html
Differential Revision: http://reviews.llvm.org/D21798
llvm-svn: 274742
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/macros/TestMacros.py')
0 files changed, 0 insertions, 0 deletions