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

diff --git a/gcc/testsuite/gfortran.dg/c_ptr_tests_9.f03 b/gcc/testsuite/gfortran.dg/c_ptr_tests_9.f03
new file mode 100644
index 000000000..f72349264
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/c_ptr_tests_9.f03
@@ -0,0 +1,32 @@
+! { dg-do run }
+! { dg-options "-std=gnu" }
+! This test is pretty simple but is here just to make sure that the changes 
+! done to c_ptr and c_funptr (translating them to void *) works in the case 
+! where a component of a type is of type c_ptr or c_funptr.  
+module c_ptr_tests_9
+  use, intrinsic :: iso_c_binding, only: c_ptr, c_null_ptr
+
+  type myF90Derived
+     type(c_ptr) :: my_c_ptr
+  end type myF90Derived
+
+contains
+  subroutine sub0() bind(c)
+    type(myF90Derived), target :: my_f90_type
+    type(myF90Derived), pointer :: my_f90_type_ptr
+
+    my_f90_type%my_c_ptr = c_null_ptr
+    print *, 'my_f90_type is: ', my_f90_type
+    my_f90_type_ptr => my_f90_type
+    print *, 'my_f90_type_ptr is: ', my_f90_type_ptr
+  end subroutine sub0
+end module c_ptr_tests_9
+
+
+program main
+  use c_ptr_tests_9
+
+  call sub0()
+end program main
+
+! { dg-final { cleanup-modules "c_ptr_tests_9" } }