We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a ticket to keep a track of errors and slowness from check-openmp when I enable libcxx/libcxxabi/libuwind/openmp using upstream's main.
The text was updated successfully, but these errors were encountered:
No errors after applying several local patches. I'll upstream them as soon as possible.
-- Testing: 317 tests, 24 workers -- Testing: 0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. ******************** Unsupported Tests (111): libomp :: atomic/kmp_atomic_float10_max_min.c ... libomp :: teams/teams.c Testing Time: 1746.03s Unsupported: 111 Passed : 206
The execution time is really slow. These tests run in about 30sec on x86.
Sorry, something went wrong.
Slow tests more than 1 elapsed min are below:
/scratch/jam/llvm-dev/build-zorg/build_llvm/runtimes/runtimes-ve-unknown-linux-gnu-bins/openmp/runtime/test/tasking/hidden_helper_task/Output/depend.cpp.tmp 0.27user 0.59system 8:42.71elapsed 0%CPU (0avgtext+0avgdata 58284maxresident)k /scratch/jam/llvm-dev/build-zorg/build_llvm/runtimes/runtimes-ve-unknown-linux-gnu-bins/openmp/runtime/test/tasking/hidden_helper_task/Output/gtid.cpp.tmp 0.17user 0.34system 6:59.36elapsed 0%CPU (0avgtext+0avgdata 58300maxresident)k /scratch/jam/llvm-dev/build-zorg/build_llvm/runtimes/runtimes-ve-unknown-linux-gnu-bins/openmp/runtime/test/worksharing/for/Output/kmp_sch_simd_guided.c.tmp 65.87user 175.37system 3:26.13elapsed 117%CPU (0avgtext+0avgdata 41532maxresident)k
No branches or pull requests
This is a ticket to keep a track of errors and slowness from check-openmp when I enable libcxx/libcxxabi/libuwind/openmp using upstream's main.
The text was updated successfully, but these errors were encountered: