Re: [PATCH][OpenMP] Fix resolve_device with -foffload=disable

2015-06-17 Thread Thomas Schwinge
Hi! On Mon, 1 Jun 2015 17:04:03 +0300, Ilya Verbin iver...@gmail.com wrote: Is this change ok for OpenACC/PTX? Well, it doesn't cause any visible regressions in libgomp testing for OpenACC, so OK from that point of view. The code that you're changing is not actually used for OpenACC; I first

Re: [PATCH][OpenMP] Fix resolve_device with -foffload=disable

2015-06-01 Thread Ilya Verbin
Hi, Thomas! Is this change ok for OpenACC/PTX? On Mon, Apr 20, 2015 at 17:16:03 +0300, Ilya Verbin wrote: Currently if a compiler is configured with enabled offloading, the 'devices' array in libgomp is filled properly with a number of available devices. However, if a program is compiled with

Re: [PATCH][OpenMP] Fix resolve_device with -foffload=disable

2015-04-27 Thread Ilya Verbin
On Mon, Apr 20, 2015 at 17:16:03 +0300, Ilya Verbin wrote: Hi! Currently if a compiler is configured with enabled offloading, the 'devices' array in libgomp is filled properly with a number of available devices. However, if a program is compiled with -foffload=disable, the resolve_device

[PATCH][OpenMP] Fix resolve_device with -foffload=disable

2015-04-20 Thread Ilya Verbin
Hi! Currently if a compiler is configured with enabled offloading, the 'devices' array in libgomp is filled properly with a number of available devices. However, if a program is compiled with -foffload=disable, the resolve_device function returns a pointer to the device, and host-fallback is not