--- Comment #6 from jv244 at cam dot ac dot uk 2010-07-08 06:24 ---
I have also tried to run the testcase with
export OMP_WAIT_POLICY=active
export GOMP_SPINCOUNT=infinity
which I would assume to keep the threads alive, and so there would be no need
to create these new threads (the nu
--- Comment #7 from jakub at gcc dot gnu dot org 2010-07-08 07:54 ---
Currently libgomp terminates all threads immediately, unless mandated by the
standard (i.e. in non-nested case the threads need to be kept around until next
omp parallel).
Yes, it would be possible to keep other threa
--- Comment #8 from jv244 at cam dot ac dot uk 2010-07-08 08:55 ---
(In reply to comment #7)
> Yes, it would be possible to keep other threads around, the question is how
> many and how long, at which point start to destroy them.
I can test what other implementations are doing, but I su
--- Comment #1 from jv244 at cam dot ac dot uk 2010-07-06 08:03 ---
Created an attachment (id=21099)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21099&action=view)
testcase part 1
C code to report thread binding
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44833
--- Comment #2 from jv244 at cam dot ac dot uk 2010-07-06 08:05 ---
Created an attachment (id=21100)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21100&action=view)
fortran testcase
build & run testcase as :
gfortran -fopenmp test.f90 get_affinity.c
export OMP_NUM_THREADS=8
expo
--- Comment #3 from jakub at gcc dot gnu dot org 2010-07-06 08:21 ---
That's how GOMP_CPU_AFFINITY works - it is a round-robin assignment of CPUs
upon thread creation, and the first two threads are never recreated in this
case.
Currently there is no tracking on how many threads bind to w
--- Comment #4 from jv244 at cam dot ac dot uk 2010-07-06 10:01 ---
(In reply to comment #3)
> That's how GOMP_CPU_AFFINITY works - it is a round-robin assignment of CPUs
> upon thread creation, and the first two threads are never recreated in this
> case.
> Currently there is no trackin
--- Comment #5 from jv244 at cam dot ac dot uk 2010-07-06 11:32 ---
I also checked the pgi and cray compilers, they all lead to iforts thread
binding.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44833
