This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Thread pool libgomp (openmp)


When changing the number of threads dynamically in OpenMP, I've seen that
if the next region has fewer threads than the previous, the exceed is left
to die. So, in the future, if another region needs more threads is
necessary calling pthread_create() again. Why doesn't libgomp maintains the
exceed threads in the pool to reuse case necessary?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]