diff options
| author | Eli Friedman <efriedma@codeaurora.org> | 2018-04-16 23:52:58 +0000 |
|---|---|---|
| committer | Eli Friedman <efriedma@codeaurora.org> | 2018-04-16 23:52:58 +0000 |
| commit | 642a5ee1c1b74fb98a2140ca90ea5a934762c7da (patch) | |
| tree | fd4a7f6d0be39e7dd2f4c3a2f593b0ea0700b0a5 /lldb/packages/Python/lldbsuite/test/functionalities/stats_api | |
| parent | 7a44782c73589fca669e04afb5e563b92a7ff4de (diff) | |
| download | bcm5719-llvm-642a5ee1c1b74fb98a2140ca90ea5a934762c7da.tar.gz bcm5719-llvm-642a5ee1c1b74fb98a2140ca90ea5a934762c7da.zip | |
[ARM] Compute a target feature which corresponds to the ARM version.
Currently, the interaction between the triple, the CPU, and the
supported features is a mess: the driver edits the triple to indicate
the supported architecture version, and the LLVM backend uses this to
figure out what instructions are legal. This makes it difficult to
understand what's happening, and makes it impossible to LTO together two
modules with different computed architectures.
Instead of relying on triple rewriting to get the correct target
features, we should add the right target features explicitly.
Differential Revision: https://reviews.llvm.org/D45240
llvm-svn: 330169
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/stats_api')
0 files changed, 0 insertions, 0 deletions
