Re: [gomp4] Another oacc reduction simplification

On 09/24/15 16:32, Cesar Philippidis wrote: On 09/22/2015 08:29 AM, Nathan Sidwell wrote: 1) Don't have a fake gang reduction outside of worker & vector loops. Deal with the receiver object directly. I.e. 'ref_to_res' need not be a null pointer for vector and worker loops. What happens when

Re: [gomp4] Another oacc reduction simplification

On 09/25/2015 03:57 AM, Nathan Sidwell wrote: > On 09/24/15 16:32, Cesar Philippidis wrote: >> On 09/22/2015 08:29 AM, Nathan Sidwell wrote: >> >>> 1) Don't have a fake gang reduction outside of worker & vector loops. >>> Deal with the receiver object directly. I.e. 'ref_to_res' need not be a >>>

Re: [gomp4] Another oacc reduction simplification

On 09/22/2015 08:29 AM, Nathan Sidwell wrote: > 1) Don't have a fake gang reduction outside of worker & vector loops. > Deal with the receiver object directly. I.e. 'ref_to_res' need not be a > null pointer for vector and worker loops. What happens when there is no receiver object. E.g. a

Re: [gomp4] Another oacc reduction simplification

On 09/23/15 04:02, Thomas Schwinge wrote: Hi! On Tue, 22 Sep 2015 11:29:37 -0400, Nathan Sidwell wrote: I've committed this patch, which simplifies the generation of openacc reduction code. Aside from the progression mentioned in

Re: [gomp4] Another oacc reduction simplification

Hi! On Tue, 22 Sep 2015 11:29:37 -0400, Nathan Sidwell wrote: > I've committed this patch, which simplifies the generation of openacc > reduction > code. Aside from the progression mentioned in

[gomp4] Another oacc reduction simplification

I've committed this patch, which simplifies the generation of openacc reduction code. Primarily three changes 1) Don't have a fake gang reduction outside of worker & vector loops. Deal with the receiver object directly. I.e. 'ref_to_res' need not be a null pointer for vector and worker