https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
--- Comment #6 from Jakub Jelinek ---
(In reply to Alexander Monakov from comment #5)
> Can libgomp defer changing affinity of the initial thread to the launch of
> the first parallel region (i.e. change it only at thread pool
> initialization,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
--- Comment #4 from Stijn De Weirdt ---
hi jakub,
thanks for the explanation. so if i understand this, the main thread/process of
any binary linked with libgomp becomes an OpenMP thread, because of the libgomp
constructor doing something. and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
--- Comment #3 from Jakub Jelinek ---
(In reply to Stijn De Weirdt from comment #2)
> apologies for my ignorance, but how is working as expected? i can't make
> this up from the description of the variable; and it's unexpected since
> there is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
--- Comment #2 from Stijn De Weirdt ---
hi jakub,
apologies for my ignorance, but how is working as expected? i can't make this
up from the description of the variable; and it's unexpected since there is no
openmp code being run (naively then;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114765
--- Comment #1 from Jakub Jelinek ---
That is how it should behave. Don't use OMP_PROC_BIND=true unless that is what
you want...
