Re: [committed] openmp: Conforming device numbers and omp_{initial,invalid}_device

2022-06-15 Thread Thomas Schwinge
Hi Jakub! On 2022-06-15T10:46:30+0200, Jakub Jelinek wrote: > On Tue, Jun 14, 2022 at 06:41:37PM +0200, Thomas Schwinge wrote: >> On 2022-06-13T14:06:39+0200, Jakub Jelinek via Gcc-patches >> wrote: >> > OpenMP 5.2 changed once more what device numbers are allowed. >> >> > libgomp/ >> >> >

Re: [committed] openmp: Conforming device numbers and omp_{initial,invalid}_device

2022-06-15 Thread Jakub Jelinek via Gcc-patches
On Tue, Jun 14, 2022 at 06:41:37PM +0200, Thomas Schwinge wrote: > Hi Jakub! > > On 2022-06-13T14:06:39+0200, Jakub Jelinek via Gcc-patches > wrote: > > OpenMP 5.2 changed once more what device numbers are allowed. > > > libgomp/ > > > * testsuite/libgomp.c-c++-common/target-is-accessibl

Re: [committed] openmp: Conforming device numbers and omp_{initial, invalid}_device

2022-06-14 Thread Thomas Schwinge
Hi Jakub! On 2022-06-13T14:06:39+0200, Jakub Jelinek via Gcc-patches wrote: > OpenMP 5.2 changed once more what device numbers are allowed. > libgomp/ > * testsuite/libgomp.c-c++-common/target-is-accessible-1.c (main): Add > test with omp_initial_device. Use -5 instead of -1 for n

[committed] openmp: Conforming device numbers and omp_{initial,invalid}_device

2022-06-13 Thread Jakub Jelinek via Gcc-patches
Hi! OpenMP 5.2 changed once more what device numbers are allowed. In 5.1, valid device numbers were [0, omp_get_num_devices()]. 5.2 makes also -1 valid (calls it omp_initial_device), which is equivalent in behavior to omp_get_num_devices() number but has the advantage that it is a constant. And i