[PING^2][PATCH, 12/16] Handle acc loop directive

2016-03-14 Thread Tom de Vries
On 07/03/16 09:21, Tom de Vries wrote: On 29/02/16 04:26, Tom de Vries wrote: On 22-02-16 11:57, Jakub Jelinek wrote: On Mon, Feb 22, 2016 at 11:54:46AM +0100, Tom de Vries wrote: Following up on your suggestion to implement this during gimplification, I wrote attached patch. I'll put it

[PING][PATCH, 12/16] Handle acc loop directive

2016-03-07 Thread Tom de Vries
On 29/02/16 04:26, Tom de Vries wrote: On 22-02-16 11:57, Jakub Jelinek wrote: On Mon, Feb 22, 2016 at 11:54:46AM +0100, Tom de Vries wrote: Following up on your suggestion to implement this during gimplification, I wrote attached patch. I'll put it through some openacc testing and add

Re: [PING^3][PATCH, 12/16] Handle acc loop directive

2016-02-28 Thread Tom de Vries
On 22-02-16 11:57, Jakub Jelinek wrote: On Mon, Feb 22, 2016 at 11:54:46AM +0100, Tom de Vries wrote: Following up on your suggestion to implement this during gimplification, I wrote attached patch. I'll put it through some openacc testing and add testcases. Is this approach acceptable for

Re: [PING^3][PATCH, 12/16] Handle acc loop directive

2016-02-22 Thread Jakub Jelinek
On Mon, Feb 22, 2016 at 11:54:46AM +0100, Tom de Vries wrote: > Following up on your suggestion to implement this during gimplification, I > wrote attached patch. > > I'll put it through some openacc testing and add testcases. Is this approach > acceptable for stage4? LGTM. > gcc/gimplify.c |

Re: [PING^3][PATCH, 12/16] Handle acc loop directive

2016-02-22 Thread Tom de Vries
On 12/02/16 12:10, Tom de Vries wrote: On 26/01/16 13:49, Jakub Jelinek wrote: On Tue, Jan 26, 2016 at 01:38:39PM +0100, Tom de Vries wrote: Ping^3. ( https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01089.html ) First of all, I wonder if it wouldn't be far easier to handle these during

Re: [PING^3][PATCH, 12/16] Handle acc loop directive

2016-02-12 Thread Tom de Vries
On 26/01/16 13:49, Jakub Jelinek wrote: On Tue, Jan 26, 2016 at 01:38:39PM +0100, Tom de Vries wrote: Ping^3. ( https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01089.html ) First of all, I wonder if it wouldn't be far easier to handle these during gimplification rather than during omp expansion

[PING^3][PATCH, 12/16] Handle acc loop directive

2016-01-26 Thread Tom de Vries
On 18/01/16 15:27, Tom de Vries wrote: On 24/11/15 13:26, Tom de Vries wrote: On 09/11/15 21:06, Tom de Vries wrote: On 09/11/15 16:35, Tom de Vries wrote: Hi, this patch series for stage1 trunk adds support to: - parallelize oacc kernels regions using parloops, and - map the loops onto the

Re: [PING^3][PATCH, 12/16] Handle acc loop directive

2016-01-26 Thread Jakub Jelinek
On Tue, Jan 26, 2016 at 01:38:39PM +0100, Tom de Vries wrote: > Ping^3. ( https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01089.html ) First of all, I wonder if it wouldn't be far easier to handle these during gimplification rather than during omp expansion or during parsing. Inside kernels, do

[PING^2][PATCH, 12/16] Handle acc loop directive

2016-01-18 Thread Tom de Vries
On 24/11/15 13:26, Tom de Vries wrote: On 09/11/15 21:06, Tom de Vries wrote: On 09/11/15 16:35, Tom de Vries wrote: Hi, this patch series for stage1 trunk adds support to: - parallelize oacc kernels regions using parloops, and - map the loops onto the oacc gang dimension. The patch series

[PING][PATCH, 12/16] Handle acc loop directive

2015-11-24 Thread Tom de Vries
On 09/11/15 21:06, Tom de Vries wrote: On 09/11/15 16:35, Tom de Vries wrote: Hi, this patch series for stage1 trunk adds support to: - parallelize oacc kernels regions using parloops, and - map the loops onto the oacc gang dimension. The patch series contains these patches: 1

[PATCH, 12/16] Handle acc loop directive

2015-11-09 Thread Tom de Vries
On 09/11/15 16:35, Tom de Vries wrote: Hi, this patch series for stage1 trunk adds support to: - parallelize oacc kernels regions using parloops, and - map the loops onto the oacc gang dimension. The patch series contains these patches: 1Insert new exit block only when needed in