I discovered these two tests try and set an unreasonable vector_length. They're
attempting to check reduction behaviour, so I've applied this patch to trunk to
reduce the vector length.
I already fixed them on the gomp4 branch, and additional functionality there
will give a diagnostic on such a large vector length. But that's a check for a
different testcase.
nathan
2015-10-20 Nathan Sidwell <nat...@codesourcery.com>
* testsuite/libgomp.oacc-c-c++-common/reduction-5.c: Set sane
vector_length.
* testsuite/libgomp.oacc-fortran/reduction-6.f90: Likewise.
Index: libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-5.c
===================================================================
--- libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-5.c (revision 228969)
+++ libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-5.c (working copy)
@@ -8,7 +8,7 @@ main (void)
int n = 100;
int i;
-#pragma acc parallel vector_length (1000)
+#pragma acc parallel vector_length (32)
#pragma acc loop reduction (+:s1, s2)
for (i = 0; i < n; i++)
{
@@ -29,4 +29,4 @@ main (void)
abort ();
return 0;
-}
\ No newline at end of file
+}
Index: libgomp/testsuite/libgomp.oacc-fortran/reduction-6.f90
===================================================================
--- libgomp/testsuite/libgomp.oacc-fortran/reduction-6.f90 (revision 228969)
+++ libgomp/testsuite/libgomp.oacc-fortran/reduction-6.f90 (working copy)
@@ -11,7 +11,7 @@ program reduction
vs1 = 0
vs2 = 0
- !$acc parallel vector_length (1000)
+ !$acc parallel vector_length (32)
!$acc loop reduction(+:s1, s2)
do i = 1, n
s1 = s1 + 1
