On Mon, Nov 02, 2015 at 11:38:47AM -0500, Nathan Sidwell wrote:
> This patch are the initial set of tests. The libgomp tests use an idiom of
> summing thread identifiers and then checking the expected set of threads
> participated. They are all derived from the loop tests I recently added for
> the execution model itself.
>
> The fortran test was duplicated in both the gfortran testsuite and the
> libgomp testsuite. I deleted it from the former. It was slightly bogus as
> it asked for a vector-length of 40, and appeared to be working by accident
> by not actually partitioning the loop. I fixed that up and reworked it to
> avoid needing a reduction on a reference variable. Reference handling will
> be a later patch.
>
> nathan
> 2015-11-02 Nathan Sidwell <nat...@codesourcery.com>
>
> libgomp/
> * libgomp.oacc-c-c++-common/loop-red-g-1.c: New.
> * libgomp.oacc-c-c++-common/loop-red-gwv-1.c: New.
> * libgomp.oacc-c-c++-common/loop-red-v-1.c: New.
> * libgomp.oacc-c-c++-common/loop-red-v-2.c: New.
> * libgomp.oacc-c-c++-common/loop-red-w-1.c: New.
> * libgomp.oacc-c-c++-common/loop-red-w-2.c: New.
> * libgomp.oacc-c-c++-common/loop-red-wv-1.c: New.
> * libgomp.oacc-fortran/reduction-5.f90: Avoid reference var.
>
> gcc/testsuite/
> * gfortran.dg/goacc/reduction-2.f95: Delete.
Ok.
Jakub
