Thread pool libgomp (openmp)

Charles Cardoso charlesoc94@gmail.com
Wed May 16 18:33:00 GMT 2018


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?



More information about the Gcc-help mailing list