diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gfortran.dg/pr15164.f90 | |
download | cbb-gcc-4.6.4-upstream.tar.bz2 cbb-gcc-4.6.4-upstream.tar.xz |
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.
Diffstat (limited to 'gcc/testsuite/gfortran.dg/pr15164.f90')
-rw-r--r-- | gcc/testsuite/gfortran.dg/pr15164.f90 | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/gcc/testsuite/gfortran.dg/pr15164.f90 b/gcc/testsuite/gfortran.dg/pr15164.f90 new file mode 100644 index 000000000..f8098710b --- /dev/null +++ b/gcc/testsuite/gfortran.dg/pr15164.f90 @@ -0,0 +1,17 @@ +! { dg-do compile } +! I couldn't reproduce the failure with a compiler built from the +! 2004-09-26 sources + module specfiles + contains + subroutine split(instring,outstrings,lenout,n,i) + integer(kind=4),intent(in) :: lenout,n + character(len=*),intent(in) :: instring + character(len=lenout),dimension(n),intent(out) :: outstrings + integer(kind=4) :: i,j,k + j=1; k=1 + outstrings(j)(k:k)=instring(i:i) + return + end subroutine split + end module specfiles + +! { dg-final { cleanup-modules "specfiles" } } |