This patch fixes https://bugs.llvm.org/show_bug.cgi?id=42906, via adding adjustment of number of threads on enter to the teams construct on host according to user settings. This allows to pass checks and avoid assertions at time of team of threads creation.
Details
Details
- Reviewers
jlpeyton tlwilmar hbae jdoerfert - Commits
- rOMP369430: Force honoring nthreads-var and thread-limit-var inside teams construct on host
rG57ae6b8e377c: Force honoring nthreads-var and thread-limit-var inside teams construct on host
rL369430: Force honoring nthreads-var and thread-limit-var inside teams construct on host
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Sorry for late reply, I was on vacation w/o internet access.
I guess no. We are probably missing 9.0 release. Do you think it is important enough to request its pull at this (late) stage of the release process?
Comment Actions
I think this can wait at this point. I noticed the problem on Power when I was doing performance tests. On Power using all the available threads (including HT) was causing slow downs with SPEC Accel OMP, so I had to set the OMP_THREAD_LIMIT and noticed the seg faults. I can patch my own runtime and wait for the next release that will integrate this fix. Thanks!
Comment Actions
BTW, there is also workaround without runtime patching, - set KMP_TEAMS_THREAD_LIMIT to the same value as OMP_THREAD_LIMIT. This avoids runtime segfault with old library.