diff options
author | Todd Fiala <todd.fiala@gmail.com> | 2014-09-25 19:25:07 +0000 |
---|---|---|
committer | Todd Fiala <todd.fiala@gmail.com> | 2014-09-25 19:25:07 +0000 |
commit | b3185e710e797b441c042a942d812eaf6b01ad4a (patch) | |
tree | b29c7d86ca2a591ec7465edbedcf19ac85ff37f5 /llvm/lib/CodeGen/MachineSink.cpp | |
parent | 1fa1ce6112a5a1550b107daae3d9ddd7017dd25c (diff) | |
download | llvm-b3185e710e797b441c042a942d812eaf6b01ad4a.zip llvm-b3185e710e797b441c042a942d812eaf6b01ad4a.tar.gz llvm-b3185e710e797b441c042a942d812eaf6b01ad4a.tar.bz2 |
Fixup gtest layout, add Linux ThreadStateCoordinator.cpp.
This change does the following:
* Remove test/c++/...
* Add gtest.
* Add gtest/unittest directory for unittesting individual classes.
* Add an initial Plugins/Process?linux/ThreadStateCoordinatorTest.cpp.
- currently failing a test (intentional).
- added a bare-bones ThreadStateCoordinator.cpp to Plugins/Process/Linux,
more soon. Just enough to prove out running gtest on Ubuntu and MacOSX.
* Added recursive make machinery so that doing a 'make' in gtest/ is
sufficient to kick off the existing test several directories down.
- Caveat - I currently short circuit from gtest/unittest/Makefile directly to
the one and only gtest/unittest/Plugins/Process/Linux directory. We'll need
to add the intervening layers. I haven't done this yet since to fix the
Xcode test failure correspondence, I may need to add a python layer which
might just handle the directory crawling.
* Added an Xcode project to the lldb workspace for gtest.
- Runs the recursive make system in gtest/Makefile.
- Default target is 'test'. test and clean are supported.
- Currently does not support test failure file/line correspondence.
Requires a bit of text transformation to hook that up.
llvm-svn: 218460
Diffstat (limited to 'llvm/lib/CodeGen/MachineSink.cpp')
0 files changed, 0 insertions, 0 deletions