This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Patch, Fortran, committed] Remove bogus dg-error in gfortran.dg/coarray_lock_3.f90


Hi all,

when committing the LOCK patch, I forgot to include attached change in the testsuite, which causes testsuite failures.

I planned to correct that together with other constraint-check issues, but obviously I haven't done so for several weeks. Thus, I decided to start by fixing the test suite. (The line is indeed OK, i.e. the just committed patch is correct.)

There are still some issues with LOCK_TYPE checking, in particular with LOCK_TYPES in derived types.

Committed as Rev. 176137.

Tobias
Index: gcc/testsuite/gfortran.dg/coarray_lock_3.f90
===================================================================
--- gcc/testsuite/gfortran.dg/coarray_lock_3.f90	(revision 176136)
+++ gcc/testsuite/gfortran.dg/coarray_lock_3.f90	(working copy)
@@ -69,7 +69,7 @@
   lock(lock)
   lock(lock2(1))
   lock(lock2) ! { dg-error "must be a scalar coarray of type LOCK_TYPE" }
-  lock(lock[1]) ! { dg-error "must be a scalar coarray of type LOCK_TYPE" }
+  lock(lock[1]) ! OK
 end subroutine lock_test2
 
 
Index: gcc/testsuite/ChangeLog
===================================================================
--- gcc/testsuite/ChangeLog	(revision 176136)
+++ gcc/testsuite/ChangeLog	(working copy)
@@ -1,3 +1,8 @@
+2011-07-11  Tobias Burnus  <burnus@net-b.de>
+
+	PR fortran/18918
+	* gfortran.dg/coarray_lock_3.f90: Remove bogus dg-error.
+
 2011-07-11  Georg-Johann Lay  <avr@gjlay.de>
 	
 	* lib/target-supports.exp (check_effective_target_scheduling):

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]