[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-06-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-06-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #15 from Jakub Jelinek --- Author: jakub Date: Thu Jun 22 11:11:43 2017 New Revision: 249508 URL: https://gcc.gnu.org/viewcvs?rev=249508=gcc=rev Log: Backported from mainline 2017-05-30 Jakub Jelinek

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-06-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #14 from Jakub Jelinek --- Fixed for 7.2+ so far.

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-06-02 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #13 from Jakub Jelinek --- Author: jakub Date: Fri Jun 2 07:27:49 2017 New Revision: 248814 URL: https://gcc.gnu.org/viewcvs?rev=248814=gcc=rev Log: Backported from mainline 2017-05-30 Jakub Jelinek

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #12 from Jakub Jelinek --- Author: jakub Date: Tue May 30 12:05:30 2017 New Revision: 248683 URL: https://gcc.gnu.org/viewcvs?rev=248683=gcc=rev Log: PR libgomp/80822 * config/linux/affinity.c

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-26 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #11 from Jakub Jelinek --- Should apply cleanly against 6.x, 7.x as well as current trunk.

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-26 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-26 Thread weeks at iastate dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #9 from Nathan Weeks --- Created attachment 41423 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41423=edit Code from 80822 comment #4 run as per comment #8

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-26 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #8 from Jakub Jelinek --- (In reply to Nathan Weeks from comment #6) > Created attachment 41417 [details] > output from comment #4 code compiled with Intel 17.0.2 Could I ask you for output of additional: for i in `seq 64`; do echo

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-25 Thread weeks at iastate dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #7 from Nathan Weeks --- The Cray 8.5.4 compiler supports only OpenMP 4.0, and so lacks support for omp_get_num_places(), omp_get_place_num_procs(), and omp_get_place_proc_ids().

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-25 Thread weeks at iastate dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #6 from Nathan Weeks --- Created attachment 41417 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41417=edit output from comment #4 code compiled with Intel 17.0.2

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-25 Thread weeks at iastate dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #5 from Nathan Weeks --- Created attachment 41416 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41416=edit output from comment #4 code compiled with gcc 6.3.0

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-25 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #4 from Jakub Jelinek --- That just means they don't provide really helpful information on what they expand threads to. Can you try: #include #include #include int main () { int num_places = omp_get_num_places (), i, j;

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-24 Thread weeks at iastate dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #3 from Nathan Weeks --- Setting OMP_DISPLAY_ENV=verbose results in the following output with Intel 17.0.2: OPENMP DISPLAY ENVIRONMENT BEGIN

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #2 from Jakub Jelinek --- Note, the OpenMP description of OMP_PLACES=threads is: "Each place corresponds to a single hardware thread on the target machine." which is what GCC implements. Perhaps ICC implements the same, but orders

[Bug libgomp/80822] libgomp incorrect affinity when OMP_PLACES=threads

2017-05-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80822 --- Comment #1 from Jakub Jelinek --- What do you get with OMP_PLACES=threads OMP_DISPLAY_ENV=verbose (with both libgomp and Intel libomp)?