Hi!
On Wed, 10 May 2017 18:28:38 +0200, Jakub Jelinek wrote:
> On Mon, May 08, 2017 at 09:29:28PM +0200, Thomas Schwinge wrote:
> > Use "oacc kernels" attribute for OpenACC kernels
> > * omp-expand.c (expand_omp_target)
> > : Set &
On Tue, May 09, 2017 at 10:57:34PM +0200, Thomas Schwinge wrote:
> commit b6b5d549089423e3fbe387f63467d052b956f3f7
> Author: Thomas Schwinge
> Date: Tue May 9 20:14:03 2017 +0200
>
> Use "oacc kernels parallelized" attribute for parallelized OpenACC kernels
>
> gcc/
>
On Mon, May 08, 2017 at 09:29:28PM +0200, Thomas Schwinge wrote:
> commit fac5c3214f58812881635d3fb1e1751446d4b660
> Author: Thomas Schwinge
> Date: Mon May 8 21:24:46 2017 +0200
>
> Use "oacc kernels" attribute for OpenACC kernels
>
> gc
KIND_OACC_PARALLEL) into BUILT_IN_GOACC_PARALLEL. My
> > > reasoning for not setting the attribute earlier (like, in the front
> > > ends), is that at that point in/before expand_omp_target, we still have
> > > the distrinction between OACC_PARALLEL/OACC_KERNELS (tre
RALLEL/OACC_KERNELS (tree codes), and
> > later GF_OMP_TARGET_KIND_OACC_PARALLEL/GF_OMP_TARGET_KIND_OACC_KERNELS
> > (GIMPLE_OMP_TARGET subcodes). Another question/possibly cleanup of
> > course might be to actually do set the "oacc kernels" attribute in the
> > f
on between OACC_PARALLEL/OACC_KERNELS (tree codes), and
> later GF_OMP_TARGET_KIND_OACC_PARALLEL/GF_OMP_TARGET_KIND_OACC_KERNELS
> (GIMPLE_OMP_TARGET subcodes). Another question/possibly cleanup of
> course might be to actually do set the "oacc kernels" attribute in the
> fron
t;oacc kernels" attribute in the
front end and merge OACC_KERNELS into OACC_PARALLEL, and
GF_OMP_TARGET_KIND_OACC_KERNELS into GF_OMP_TARGET_KIND_OACC_PARALLEL?
But anyway, as a first step: OK for trunk?
commit 2e6dc8dfd679d8dae814e325afa2547b502827ef
Author: Thomas Schwinge
Date: Tue Jul 26 17:44:31 2016 +020