https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698
--- Comment #4 from kugan at gcc dot gnu.org ---
Thanks for looking into this. The main reason we ere seeing performance issue
turned out to be due to glibc malloc issue in
https://sourceware.org/bugzilla/show_bug.cgi?id=30945
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698
--- Comment #3 from Jakub Jelinek ---
You can use GOMP_CPU_AFFINITY or different setting of OMP_PROC_BIND together
with OMP_PLACES to bind the initial thread to different CPU.
While the OpenMP spec allows moving the initial thread from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698
--- Comment #2 from Andrew Pinski ---
Actually I misread the testcase, because it looks like LLVM's libomp follows
the same as GCC's.
And it looks like the OpenMP spec is specific about that behavior too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698
--- Comment #1 from Andrew Pinski ---
https://www.openmp.org/spec-html/5.0/openmpse52.html
> Otherwise, the execution environment should not move OpenMP threads between
> OpenMP places, thread affinity is enabled, and __the initial thread is
