summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities/thread/create_after_attach/TestCreateAfterAttach.py
diff options
context:
space:
mode:
authorDaniel Sanders <daniel.sanders@imgtec.com>2015-07-06 16:56:07 +0000
committerDaniel Sanders <daniel.sanders@imgtec.com>2015-07-06 16:56:07 +0000
commitf423f5627caed62aadb02ebecfc464dfb1c99097 (patch)
tree273c3214480e8465d87cb322e0703641e1dfcaaa /lldb/test/functionalities/thread/create_after_attach/TestCreateAfterAttach.py
parentef8f95417acd298a8b042dab887c8567831113f1 (diff)
downloadbcm5719-llvm-f423f5627caed62aadb02ebecfc464dfb1c99097.tar.gz
bcm5719-llvm-f423f5627caed62aadb02ebecfc464dfb1c99097.zip
Change the last few internal StringRef triples into Triple objects.
Summary: This concludes the patch series to eliminate StringRef forms of GNU triples from the internals of LLVM that began in r239036. At this point, the StringRef-form of GNU Triples should only be used in the public API (including IR serialization) and a couple objects that directly interact with the API (most notably the Module class). The next step is to replace these Triple objects with the TargetTuple object that will represent our authoratative/unambiguous internal equivalent to GNU Triples. Reviewers: rengolin Subscribers: llvm-commits, jholewinski, ted, rengolin Differential Revision: http://reviews.llvm.org/D10962 llvm-svn: 241472
Diffstat (limited to 'lldb/test/functionalities/thread/create_after_attach/TestCreateAfterAttach.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud