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/fmt_t_6.f | |
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/fmt_t_6.f')
-rw-r--r-- | gcc/testsuite/gfortran.dg/fmt_t_6.f | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/gcc/testsuite/gfortran.dg/fmt_t_6.f b/gcc/testsuite/gfortran.dg/fmt_t_6.f new file mode 100644 index 000000000..04141a155 --- /dev/null +++ b/gcc/testsuite/gfortran.dg/fmt_t_6.f @@ -0,0 +1,10 @@ +! { dg-do run } +! PR34782 tab format failure to display properly (regression vs. g77) + character a(6) + character(22) :: output + data a / 'a', 'b', 'c', 'd', 'e', 'f' / + !write(*,'(a)') "123456789012345678901234567890" + write(output,'(T20,A3, T1,A4, T5,A2, T7,A2, T9,A4, T17,A2)') + 1 'a', 'b', 'c', 'd', 'e', 'f' + if (output .ne. " b c d e f a") call abort + end |