summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbdwarf.py
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2017-03-15 08:51:59 +0000
committerPavel Labath <labath@google.com>2017-03-15 08:51:59 +0000
commit6de25ec61a10cdea5b49f91ae7163833c45aacb1 (patch)
treeaf5b0dc85bbb6371118d50cfe9043423e5a611c1 /lldb/packages/Python/lldbsuite/test/lldbdwarf.py
parente51ee0668c8eec639964234a1d716e30f0449399 (diff)
downloadbcm5719-llvm-6de25ec61a10cdea5b49f91ae7163833c45aacb1.tar.gz
bcm5719-llvm-6de25ec61a10cdea5b49f91ae7163833c45aacb1.zip
dotest.py: remove the ability to specify different architectures/compilers in a single invocation
Summary: This has been broken at least since the new test result framework was added, which was over a year ago. It looks like nobody has missed it since. Removing this makes the gmodules handling code saner, as it already did not know how to handle the multiple-compilers case. My motivation for this is libc++ data formatters support on android -- I am trying make a central way of determining whether libc++ tests can be run, and without this, I would have to resort to similar hacks as the gmodules code. Reviewers: jingham, zturner Subscribers: danalbert, tfiala, lldb-commits Differential Revision: https://reviews.llvm.org/D30779 llvm-svn: 297811
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbdwarf.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud