obtained gcc-4.6.4.tar.bz2 from upstream website;upstream

verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.

downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.

if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.

1 files changed, 24 insertions, 0 deletions

diff --git a/gcc/testsuite/gfortran.dg/use_8.f90 b/gcc/testsuite/gfortran.dg/use_8.f90
new file mode 100644
index 000000000..adb265e5b
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/use_8.f90
@@ -0,0 +1,24 @@
+! { dg-do compile }
+module a
+
+  type, private, bind(C) b ! { dg-error "Expected :: in TYPE definition" }
+    integer i
+  end type b ! { dg-error "Expecting END MODULE statement" }
+
+  type, public c ! { dg-error "Expected :: in TYPE definition" }
+    integer j
+  end type c ! { dg-error "Expecting END MODULE statement" }
+
+  type, private d ! { dg-error "Expected :: in TYPE definition" }
+    integer k
+  end type b ! { dg-error "Expecting END MODULE statement" }
+
+  type, bind(C), public e ! { dg-error "Expected :: in TYPE definition" }
+    integer l
+  end type e ! { dg-error "Expecting END MODULE statement" }
+
+  type, bind(C) f ! { dg-error "Expected :: in TYPE definition" }
+    integer m
+  end type f ! { dg-error "Expecting END MODULE statement" }
+
+end module a