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, 37 insertions, 0 deletions

diff --git a/gcc/testsuite/gfortran.dg/used_dummy_types_3.f90 b/gcc/testsuite/gfortran.dg/used_dummy_types_3.f90
new file mode 100644
index 000000000..a308c0e37
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/used_dummy_types_3.f90
@@ -0,0 +1,37 @@
+! { dg-do compile }
+! This checks the fix for PR20864 in which same name, USE associated
+! derived types from different modules, with private components were
+! not recognised to be different.
+!
+! Contributed by Joost VandVondele  <jv244@cam.ac.uk>
+!==============
+  MODULE T1
+    TYPE data_type
+      SEQUENCE
+  ! private causes the types in T1 and T2 to be different 4.4.2
+      PRIVATE
+      INTEGER :: I
+    END TYPE
+  END MODULE
+
+  MODULE T2
+    TYPE data_type
+      SEQUENCE
+      PRIVATE
+      INTEGER :: I
+    END TYPE
+
+  CONTAINS
+
+    SUBROUTINE TEST(x)
+      TYPE(data_type) :: x
+    END SUBROUTINE TEST
+  END MODULE
+
+    USE T1
+    USE T2 , ONLY : TEST
+    TYPE(data_type) :: x
+    CALL TEST(x)         ! { dg-error "Type mismatch in argument" }
+  END
+
+! { dg-final { cleanup-modules "T1 T2" } }