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

diff --git a/gcc/testsuite/gfortran.dg/private_type_3.f90 b/gcc/testsuite/gfortran.dg/private_type_3.f90
new file mode 100644
index 000000000..dea35818e
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/private_type_3.f90
@@ -0,0 +1,34 @@
+! { dg-do compile }
+! { dg-options "-O0" }
+! Tests the fix for PR24207 and the problems associated
+! with the fix for PR21986. In two cases, use associated
+! public symbols were taking on the default private access
+! attribute of the local namespace. In the third, a private
+! symbol was not available to a namelist in contained 
+! procedure in the same module.
+!
+! Based on the example in PR24207.
+!
+module a
+  implicit none
+  real b
+  type :: mytype
+    integer :: c
+  end type mytype
+end module a
+module c
+  use a
+  implicit none
+  public d
+  private
+  real x
+  contains
+     subroutine d (arg_t)   ! This would cause an error
+        type (mytype) :: arg_t
+        namelist /e/ b, x   ! .... as would this.
+        read(5,e)
+	arg_t%c = 42
+     end subroutine d
+end module c
+
+! { dg-final { cleanup-modules "a c" } }