Add missing memory barrier for queuing locksOtherwise I see hangs in the omp_single_copyprivate test whencompiling in release mode. With the debug assertions, I get afailure `head > 0 && tail > 0
Add missing memory barrier for queuing locksOtherwise I see hangs in the omp_single_copyprivate test whencompiling in release mode. With the debug assertions, I get afailure `head > 0 && tail > 0`.Differential Revision: https://reviews.llvm.org/D40722llvm-svn: 320150
show more ...
Fix the nowait tests for omp for and omp singleThese tests are now modeled after the sections nowait test where threads waitto be released in the first construct (either for or single) and the las
Fix the nowait tests for omp for and omp singleThese tests are now modeled after the sections nowait test where threads waitto be released in the first construct (either for or single) and the last threadskips the last for/single construct and releases those threads. If the testfails, then it hangs because an unnecessary barrier is executed in between theconstructs.llvm-svn: 274641
Remove trailing whitespace from testsllvm-svn: 269841
OpenMP Initial testsuite change to purely llvm-lit based testingThis change introduces a check-libomp target which is based upon llvm's littest infrastructure. Each test (generated from the Univer
OpenMP Initial testsuite change to purely llvm-lit based testingThis change introduces a check-libomp target which is based upon llvm's littest infrastructure. Each test (generated from the University of Houston'sOpenMP testsuite) is compiled and then run. For each test, an exit status of 0indicates success and non-zero indicates failure. This way, FileCheck is notneeded. I've added a bit of logic to generate symlinks (libiomp5 and libgomp)in the build tree so that gcc can be tested as well. When building out-of-tree builds, the user will have to provide llvm-lit either by specifying-DLIBOMP_LLVM_LIT_EXECUTABLE or having llvm-lit in their PATH.Differential Revision: http://reviews.llvm.org/D11821llvm-svn: 248211