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/initialization_19.f90 b/gcc/testsuite/gfortran.dg/initialization_19.f90
new file mode 100644
index 000000000..2465f9b33
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/initialization_19.f90
@@ -0,0 +1,34 @@
+! { dg-do run }
+! The following program fails with 4.3.0
+! but works with 4.4.0. See:
+!
+! http://gcc.gnu.org/ml/fortran/2008-05/msg00199.html
+!
+module c
+type d
+  integer :: i=-1
+end type d
+end module c
+
+module s
+use c
+contains
+subroutine g
+ type(d) :: a
+ ! Without the following line it passes with 4.3.0:
+ print *, a%i
+ if(a%i /= -1) call abort()
+ a%i=0
+end subroutine g
+end module s
+
+program t
+use c
+use s
+
+call g
+call g
+
+end program t
+
+! ! { dg-final { cleanup-modules "c s" } }