Re: [gomp4] adjust num_gangs and add a diagnostic for unsupported num_workers

2017-02-17 Thread Alexander Monakov
On Fri, 17 Feb 2017, Cesar Philippidis wrote: > > And then, I don't specifically have a problem with discontinuing CUDA 5.5 > > support, and require 6.5, for example, but that should be a conscious > > decision. > > We should probably ditch CUDA 5.5. In fact, according to trunk's cuda.h, > it

Re: [gomp4] adjust num_gangs and add a diagnostic for unsupported num_workers

2017-02-17 Thread Cesar Philippidis
On 02/15/2017 01:29 PM, Thomas Schwinge wrote: > On Mon, 13 Feb 2017 08:58:39 -0800, Cesar Philippidis > wrote: >> @@ -952,25 +958,30 @@ nvptx_exec (void (*fn), size_t mapnum, void >> **hostaddrs, void **devaddrs, >>CUdevice dev = nvptx_thread()->ptx_dev->dev;

Re: [gomp4] adjust num_gangs and add a diagnostic for unsupported num_workers

2017-02-15 Thread Thomas Schwinge
Hi Cesar! On Mon, 13 Feb 2017 08:58:39 -0800, Cesar Philippidis wrote: > This patch does the followings: > > * Adjusts the default num_gangs to utilize more of GPU hardware. > * Teach libgomp to emit a diagnostic when num_workers isn't supported. > > [...] Thanks!

[gomp4] adjust num_gangs and add a diagnostic for unsupported num_workers

2017-02-13 Thread Cesar Philippidis
This patch does the followings: * Adjusts the default num_gangs to utilize more of GPU hardware. * Teach libgomp to emit a diagnostic when num_workers isn't supported. According to the confusing CUDA literature, it appears that the previous num_gangs wasn't fully utilizing the GPU hardware.