summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/macros/main.cpp
diff options
context:
space:
mode:
authorJonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>2016-03-22 07:22:49 +0000
committerJonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>2016-03-22 07:22:49 +0000
commitc80430111334f63b6e6af11d74305186f0c5460d (patch)
treeb48ca10d61bdd00686605cb4fff14869c8313d2e /lldb/packages/Python/lldbsuite/test/expression_command/macros/main.cpp
parentc04fc7a60ff4ea4610ea157be006c9771224a7b6 (diff)
downloadbcm5719-llvm-c80430111334f63b6e6af11d74305186f0c5460d.tar.gz
bcm5719-llvm-c80430111334f63b6e6af11d74305186f0c5460d.zip
[OMPT] Create infrastructure and add first tests for OMPT
Some basic checks next to the implementation should futher lower the possibility to introduce regressions. (Note that this would have catched the ordering issue fixed in rL258866 and pointed to rL263940.) The tests are implementation dependent in one point because they assume that thread ids are assigned in ascending order. This is not defined by the standard but currently ensured in libomp. We have to think about another way of ordering the threads should this ever be subject to change... Note that this isn't aiming at replacing the implementation independent test-suite at https://github.com/OpenMPToolsInterface/ompt-test-suite! Differential Revision: http://reviews.llvm.org/D16715 llvm-svn: 264027
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/macros/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud